Get details of a single webhook subscription on PostEverywhere (does NOT include the signing secret).
AI agents call get_webhook to retrieve information from Posteverywhere without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves webhook subscription details without creating, modifying, or deleting data. The explicit exclusion of the signing secret in the description reinforces that sensitive data is withheld, further limiting exposure.
From the tool's definition Tool name is 'get_webhook' with description stating 'Get details of a single webhook subscription' — the verb 'Get' and the retrieval-only nature confirm this is a read operation that queries existing webhook metadata without modification or side effects.
Attacks that exploit this kind of access
Get details of a single webhook subscription on PostEverywhere (does NOT include the signing secret). It is categorised as a Read tool in the Posteverywhere MCP Server, which means it retrieves data without modifying state.
Register the Posteverywhere MCP server in PolicyLayer and add a rule for get_webhook: 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 Posteverywhere. Nothing to install.
get_webhook 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 get_webhook 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 get_webhook. 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.
get_webhook is provided by the Posteverywhere MCP server (posteverywhere/mcp). 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 →