Low Risk

describe_hook

Return the packaged TSDoc documentation for a specific SDK hook, including its required permission(s). Call list_hooks first to discover available names.

Single-target operation

Part of the Addon MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call describe_hook to retrieve information from Addon without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though describe_hook only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

addon.yaml
tools:
  describe_hook:
    rules:
      - action: allow

See the full Addon policy for all 14 tools.

Tool Name describe_hook
Category Read
MCP Server Addon MCP Server
Risk Level Low

View all 14 tools →

Agents calling read-class tools like describe_hook have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the describe_hook tool do? +

Return the packaged TSDoc documentation for a specific SDK hook, including its required permission(s). Call list_hooks first to discover available names.. It is categorised as a Read tool in the Addon MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on describe_hook? +

Add a rule in your Intercept YAML policy under the tools section for describe_hook. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Addon MCP server.

What risk level is describe_hook? +

describe_hook is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit describe_hook? +

Yes. Add a rate_limit block to the describe_hook rule in your Intercept 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 describe_hook completely? +

Set action: deny in the Intercept policy for describe_hook. 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 describe_hook? +

describe_hook is provided by the Addon MCP server (@mywallpaper/addon-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Addon

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.