Return the catalogue of public SDK hooks exported by @mywallpaper/sdk-react, each with the manifest permission(s) it requires. Use this as the first call when deciding which hooks a new addon needs and what to declare in its manifest.
Part of the Addon MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call list_hooks 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 list_hooks 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.
tools:
list_hooks:
rules:
- action: allowSee the full Addon policy for all 14 tools.
Agents calling read-class tools like list_hooks have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Return the catalogue of public SDK hooks exported by @mywallpaper/sdk-react, each with the manifest permission(s) it requires. Use this as the first call when deciding which hooks a new addon needs and what to declare in its manifest.. It is categorised as a Read tool in the Addon MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for list_hooks. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Addon MCP server.
list_hooks is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_hooks 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.
Set action: deny in the Intercept policy for list_hooks. 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.
list_hooks 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.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept