Create a new record in a resource
AI agents use create_record to create or update resources in MCP Template — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Template environment.
This tool creates new data entries, which is a reversible write operation. It does not delete, destroy, or move money (thus not Destructive or Financial), nor does it execute arbitrary code or shell commands (thus not Execute). The medium severity reflects that creating records could have side effects depending on business logic and data constraints, but the operation itself is reversible through deletion or updates.
From the tool's definition Tool name is 'create_record' and description states 'Create a new record in a resource', which clearly indicates data creation functionality.
Attacks that exploit this kind of access
Create a new record in a resource. It is categorised as a Write tool in the MCP Template MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Template MCP server in PolicyLayer and add a rule for create_record: 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 MCP Template. Nothing to install.
create_record 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_record 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_record. 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_record is provided by the MCP Template MCP server (kbhuw/mcp_template). 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 →