get_paginated_webhook_history
AI agents call get_paginated_webhook_history to retrieve information from Terra Config 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 and queries webhook history—a read operation with no side effects. Pagination indicates querying existing data rather than modifying it. Even if webhook history includes sensitive timestamps or endpoints, the tool itself performs no write, execution, or destructive actions. Low severity due to information disclosure risk being contained to historical webhook metadata.
From the tool's definition Tool name 'get_paginated_webhook_history' indicates retrieval of historical webhook data with pagination. The verb 'get' and absence of modification language ('create', 'update', 'delete') confirms read-only semantics.
Attacks that exploit this kind of access
get_paginated_webhook_history. It is categorised as a Read tool in the Terra Config MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Terra Config MCP Server MCP server in PolicyLayer and add a rule for get_paginated_webhook_history: 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 Terra Config MCP Server. Nothing to install.
get_paginated_webhook_history 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_paginated_webhook_history 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_paginated_webhook_history. 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_paginated_webhook_history is provided by the Terra Config MCP Server MCP server (tryterra/terramcp). 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 →