Medium Risk

discovery_account

Check your Disco account status. Returns current plan, available credits (subscription + purchased), and payment method status. Use this to verify you have sufficient credits before running a private analysis. Args: api_key: Disco API key (disco_...). Optional if DISCOVERY_API_KEY env var is set.

Risk signalsHandles credentials or secrets (api_key)

Part of the Discovery Engine server.

discovery_account can modify Discovery Engine data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE DISCOVERY ENGINE →

Free to start. No card required.

AI agents use discovery_account to create or modify resources in Discovery Engine. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call discovery_account repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Discovery Engine.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "discovery_account": {
      "limits": [
        {
          "counter": "discovery_account_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Discovery Engine policy for all 14 tools.

Get this rule live on your own Discovery Engine server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY DISCOVERY ENGINE →

View all 14 tools →

These attack patterns abuse exactly the kind of access discovery_account gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so discovery_account only ever does what you allow.

SECURE DISCOVERY ENGINE →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the discovery_account tool do? +

Check your Disco account status. Returns current plan, available credits (subscription + purchased), and payment method status. Use this to verify you have sufficient credits before running a private analysis. Args: api_key: Disco API key (disco_...). Optional if DISCOVERY_API_KEY env var is set.. It is categorised as a Write tool in the Discovery Engine MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on discovery_account? +

Register the Discovery Engine MCP server in PolicyLayer and add a rule for discovery_account: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Discovery Engine. Nothing to install.

What risk level is discovery_account? +

discovery_account is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit discovery_account? +

Yes. Add a rate_limit block to the discovery_account rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block discovery_account completely? +

Set action: deny in the PolicyLayer policy for discovery_account. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides discovery_account? +

discovery_account is provided by the Discovery Engine MCP server (leap-laboratories/discovery-engine). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Discovery Engine tool call.

Deterministic rules across all 14 Discovery Engine tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.