AI agents use create_account 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 an account is a Write operation—it creates new data that can be modified or removed later. While account creation may have downstream consequences (e.g., system access), the action itself is reversible and does not involve financial transactions, code execution, or irreversible deletion.
From the tool's definition Tool name is 'create_account' and description states 'Create an account'. The server description confirms it enables 'creating' records through the Eduframe API. This creates new account data reversibly.
Attacks that exploit this kind of access
Create an account. 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_account: 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_account 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_account 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_account. 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_account 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 →