plugin.json

{
  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
  "name": "anomity",
  "version": "0.1.0",
  "description": "Ask about your organization's AI security posture through Anomity: findings, devices, MCP servers, shadow AI accounts, exposed secrets, compliance readiness and the allowlist. Skills turn the answers into posture briefings, finding triage, device investigations and allowlist reviews.",
  "author": {
    "name": "Anomity",
    "email": "support@anomity.ai",
    "url": "https://anomity.ai"
  },
  "homepage": "https://anomity.ai/docs/#the-anomity-mcp-server",
  "repository": "https://github.com/Anomity-ai/openai-plugin",
  "license": "MIT",
  "keywords": [
    "security",
    "ai-governance",
    "shadow-ai",
    "mcp",
    "compliance"
  ],
  "extensions": {
    "com.openai": {
      "interface": {
        "displayName": "Anomity",
        "shortDescription": "AI tool risk across devices",
        "longDescription": "Anomity shows a security team every AI tool running on its managed devices: coding agents, MCP servers, skills and instruction files, browser AI use, personal versus corporate AI accounts, and the credentials those tools can reach. Sensors deployed through your device management report that inventory to the Anomity console, where policies turn it into findings. This plugin reads that data for your organization.\n\nBrief leadership. Get a posture briefing built from live data: devices reporting, open and critical findings, personal AI accounts, unknown MCP servers, plaintext secrets found, and compliance scores.\n\nTriage findings. Group open findings by the policy that raised them, rank them by severity and reach, and get the practical fix for each group.\n\nInvestigate a device. Name a laptop or a person and see the AI tools, MCP servers, findings and recent changes on that machine.\n\nReview MCP servers. See which servers are official, community or unknown, how they run, what they can reach, and how many devices use them.\n\nWork the allowlist. See what is waiting for approval across AI tools, AI sites, model providers, MCP servers, extensions, plugins and skills. Admins can approve the items they confirm, when an owner has turned that on in Anomity Settings.\n\nAudit changes and compliance. Ask what changed in your AI tooling over the last 90 days, and where you stand on SOC 2, ISO 42001, the NIST AI RMF, the EU AI Act and the OWASP LLM Top 10.\n\nYou sign in with your Anomity console account, and you see what your console role allows, scoped to your organization. Secret values never leave the device and are never returned. Every tool reads data except one: approving allowlist items, which asks you to confirm the exact items first.",
        "developerName": "Anomity",
        "category": "Security",
        "capabilities": [
          "Read your organization's AI security posture",
          "Triage policy findings",
          "Investigate a managed device",
          "Review MCP servers and AI accounts",
          "Review the audit trail and compliance readiness",
          "Approve allowlist items you confirm (admins, when enabled)"
        ],
        "websiteURL": "https://anomity.ai",
        "supportURL": "https://anomity.ai/docs/",
        "privacyPolicyURL": "https://anomity.ai/legal/privacy-policy/",
        "termsOfServiceURL": "https://anomity.ai/legal/terms-of-service/",
        "defaultPrompt": [
          "Brief me on our AI security posture for the CISO",
          "What should we fix first among our open findings?",
          "Which MCP servers on our devices should worry us?"
        ],
        "brandColor": "#0E7C6E",
        "brandColorDark": "#4FD1BD",
        "composerIcon": "./assets/logo.png",
        "logo": "./assets/logo.png"
      },
      "onboardingSkill": "./skills/get-started/SKILL.md",
      "review": {
        "test_cases": {
          "positive": [
            {
              "description": "Summarize the fleet: devices reporting and open findings.",
              "prompt": "How many of our devices report to Anomity, how many are online, and how many open and critical findings do we have?",
              "tools_triggered": "get_dashboard_overview",
              "expected_behavior": "Returns the demo organization's total, online, stale and offline device counts and its open and critical finding counts, taken from the tool result without estimates."
            },
            {
              "description": "List and group critical findings.",
              "prompt": "List our critical findings in Anomity and group them by the policy that raised them.",
              "tools_triggered": "get_findings",
              "expected_behavior": "Returns the demo organization's critical findings grouped by policy name, with the number of findings in each group and a short description of each policy."
            },
            {
              "description": "Find unknown MCP servers and how widely they are used.",
              "prompt": "Which MCP servers on our devices does Anomity classify as unknown, and on how many devices does each one run?",
              "tools_triggered": "get_mcp_inventory",
              "expected_behavior": "Returns the counts of official, community and unknown MCP servers and lists the unknown servers by name with their device counts."
            },
            {
              "description": "Show what is waiting for approval on the allowlist.",
              "prompt": "What AI tools are waiting for approval on our Anomity allowlist?",
              "tools_triggered": "get_allowlist_suggestions",
              "expected_behavior": "Lists the AI tools suggested for approval with their device counts, states the total, and says whether approving through the plugin is available to this user. Approves nothing."
            },
            {
              "description": "Report compliance readiness for one framework.",
              "prompt": "What is our SOC 2 readiness score in Anomity, and which categories are weakest?",
              "tools_triggered": "get_compliance_status",
              "expected_behavior": "Returns the SOC 2 score and evaluation date and names the categories with the fewest passing requirements, without describing requirements that cannot be assessed automatically as failures."
            }
          ],
          "negative": [
            {
              "description": "Do not trigger for writing a policy document that needs no organization data.",
              "prompt": "Draft an acceptable-use policy for generative AI tools for our employee handbook."
            },
            {
              "description": "Do not trigger for general programming help.",
              "prompt": "Write a Python function that reverses a linked list."
            },
            {
              "description": "Do not trigger for scanning a code repository, which Anomity does not do.",
              "prompt": "Scan the GitHub repository github.com/example/web-app for vulnerable dependencies."
            }
          ]
        },
        "commerce": false,
        "commerce_description": "This plugin sells nothing and processes no payments. It reads data from the user's existing Anomity organization."
      },
      "publication": {
        "release_notes": "First release of Anomity: read your organization's AI security posture, with skills for posture briefings, finding triage, device investigations, MCP server and allowlist reviews, audit trail questions and compliance readiness."
      },
      "apps": "./.app.json"
    }
  }
}