AI agents use update_option_of_custom_field 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 custom field options reversibly without deleting data or executing arbitrary code. It fits the Write category as it creates or modifies data reversibly. Severity is medium because misconfiguration could affect multiple records/workflows that depend on these custom fields, but changes are not irreversible or financial in nature.
From the tool's definition Tool name is 'update_option_of_custom_field' and description states 'Update an option of a custom field', indicating modification of existing data.
Attacks that exploit this kind of access
Update an option of a custom field. 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_option_of_custom_field: 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_option_of_custom_field 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_option_of_custom_field 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_option_of_custom_field. 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_option_of_custom_field 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 →