AI agents call get_webhook_notifications_failed to retrieve information from Eduframe without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves information about failed webhook notifications from the system. It performs a read-only operation that does not modify, delete, or execute any external actions. The verb 'Get' confirms it is a retrieval function. No data is created, modified, or destroyed, making it a Read category tool with low severity.
From the tool's definition Tool name 'get_webhook_notifications_failed' and description 'Get the failed webhook notifications' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get the failed webhook notifications. It is categorised as a Read tool in the Eduframe MCP Server, which means it retrieves data without modifying state.
Register the Eduframe MCP server in PolicyLayer and add a rule for get_webhook_notifications_failed: 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 Eduframe. Nothing to install.
get_webhook_notifications_failed 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_notifications_failed 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_notifications_failed. 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_notifications_failed is provided by the Eduframe MCP server (martijnpieters/eduframe-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 →