Get webhook details by webhook ID
AI agents call getWebhookByID to retrieve information from AMOCA Solana MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves webhook metadata and configuration by ID. It performs a read-only query operation that returns data about a registered webhook without side effects, state changes, or triggering any actions. The retrieval of webhook details poses minimal risk as it neither executes transactions, modifies data, deletes resources, nor involves financial operations.
From the tool's definition Tool name 'getWebhookByID' and description 'Get webhook details by webhook ID' indicate retrieval of existing webhook configuration data without modification, deletion, or execution of actions.
Attacks that exploit this kind of access
Get webhook details by webhook ID. It is categorised as a Read tool in the AMOCA Solana MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AMOCA Solana MCP Server MCP server in PolicyLayer and add a rule for getWebhookByID: 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.
getWebhookByID 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 getWebhookByID 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 getWebhookByID. 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.
getWebhookByID 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 →