Get details for one webhook subscription by id (e.g.
AI agents call get_webhook to retrieve information from Thesma 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 metadata about an existing webhook subscription. It performs a read-only query operation without modifying, deleting, or executing any data. The action is a simple lookup by identifier, which is a classic Read category operation. Severity is low because webhook configuration details are unlikely to contain highly sensitive information, and the operation cannot cause unintended system changes.
From the tool's definition Tool name 'get_webhook' and description 'Get details for one webhook subscription by id' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get details for one webhook subscription by id (e.g. It is categorised as a Read tool in the Thesma MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Thesma MCP Server 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 Thesma MCP Server. 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 Thesma MCP Server MCP server (thesma-dev/thesma-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 →