AI agents use update_program_edition 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 program edition records in the Eduframe system but does not permanently delete data or execute arbitrary code. Updates are reversible through subsequent corrections, placing it in the Write category. Severity is medium because misconfiguration of program editions could affect multiple enrollments and course offerings, but the changes remain remediable.
From the tool's definition Tool name 'update_program_edition' and description 'Update a program edition' indicate modification of existing data. The verb 'update' is explicitly listed in the rules as a Write operation that 'creates or modifies data reversibly'.
Attacks that exploit this kind of access
Update a program edition. 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_program_edition: 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_program_edition 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_program_edition 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_program_edition. 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_program_edition 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 →