AI agents use update_planned_course 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.
This tool modifies existing data (a planned course) in a reversible manner. It is not a read operation (retrieves data), not destructive (no deletion/purging), not an execute operation triggering external code, and not financial. The severity is medium because misuse by an AI agent could alter course schedules affecting students and operations, but the impact is limited to a single entity and reversible.
From the tool's definition Tool name 'update_planned_course' and description 'Update a planned course' indicate data modification. The action is reversible (changes can be corrected), distinguishing it from destructive operations.
Attacks that exploit this kind of access
Update a planned course. 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 update_planned_course: 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.
update_planned_course 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 update_planned_course 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 update_planned_course. 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.
update_planned_course 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 →