Create a new webhook for address activity monitoring
AI agents use createWebhook to create or update resources in AMOCA Solana MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AMOCA Solana MCP Server environment.
This tool creates a new webhook configuration, which is a reversible write operation. It establishes a monitoring endpoint but does not execute transactions, move funds, or permanently delete data. The severity is medium because misconfigured webhooks could cause monitoring of unintended addresses or trigger unintended notifications, with moderate blast radius if an agent creates malicious webhooks at scale.
From the tool's definition Tool name 'createWebhook' and description 'Create a new webhook for address activity monitoring' indicate a data creation operation that establishes a persistent monitoring configuration.
Attacks that exploit this kind of access
Create a new webhook for address activity monitoring. It is categorised as a Write tool in the AMOCA Solana MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AMOCA Solana MCP Server MCP server in PolicyLayer and add a rule for createWebhook: 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 AMOCA Solana MCP Server. Nothing to install.
createWebhook is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the createWebhook 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.
Set action: deny in the PolicyLayer policy for createWebhook. 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.
createWebhook is provided by the AMOCA Solana MCP Server MCP server (manolaz/amoca-solana-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →