AI agents use create_webhook to create or update resources in Eduframe — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Eduframe environment.
Creating a webhook registers a new event handler that will trigger external HTTP callbacks. This is a write operation because it creates a new resource (webhook configuration) that can be modified or deleted later. Severity is medium because webhooks can expose sensitive data flows and create unintended side effects if misconfigured (e.g., leaking data to external URLs), but the operation itself is reversible.
From the tool's definition Tool named 'create_webhook' with description 'Register a webhook.' The action creates a new webhook configuration, which is a reversible write operation that modifies system state by adding a new integration point.
Attacks that exploit this kind of access
Register a webhook. It is categorised as a Write tool in the Eduframe MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Eduframe MCP server in PolicyLayer and add a rule for create_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 Eduframe. Nothing to install.
create_webhook is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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 create_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.
create_webhook 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 →