AI agents use create_email_message_by_user_id 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 creates a new email message record and sends it, which is a write operation that modifies system state by adding communication data. While it doesn't permanently delete data (not Destructive) nor move money (not Financial), it does create and transmit content.
From the tool's definition Tool description states "Create and send an email message to a user" - the verb 'create' and 'send' indicate data creation and transmission of a communication artifact.
Attacks that exploit this kind of access
Create and send an email message to a user. 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_email_message_by_user_id: 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_email_message_by_user_id 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_email_message_by_user_id 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_email_message_by_user_id. 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_email_message_by_user_id 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 →