AI agents call get_planning_event 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 retrieves a single planning event record from the Eduframe API. The verb 'Get' combined with the passive retrieval description shows no side effects, state changes, or data modification.
From the tool's definition Tool name 'get_planning_event' with description 'Get an planning event record' indicates a retrieval operation with no modification capability.
Attacks that exploit this kind of access
Get an planning event record. 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_planning_event: 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_planning_event 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_planning_event 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_planning_event. 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_planning_event 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 →