Create a new record in a Dataverse table
AI agents use create_record to create or update resources in Dataverse — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dataverse environment.
This tool creates new data in a Dataverse table, which is a reversible write operation. It does not delete, execute code, or commit financial transactions. The severity is medium rather than high because record creation in a database has moderate blast radius—malicious or errant record creation could pollute data or violate business logic, but records can typically be deleted afterward.
From the tool's definition Tool name 'create_record' and description 'Create a new record in a Dataverse table' indicate data creation. The Microsoft Dataverse context shows this creates persistent records in a business application database.
Documented attack patterns abuse exactly the kind of access create_record gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Dataverse, and nothing reaches the server without passing your rules. This is the rule we recommend for create_record:
{
"version": "1",
"default": "deny",
"tools": {
"create_record": {
"limits": [
{
"counter": "create_record_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_record stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new record in a Dataverse table. It is categorised as a Write tool in the Dataverse MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Dataverse 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 Dataverse. 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 Dataverse MCP server (rededis/dataverse-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Dataverse, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
22 Dataverse tools catalogued and risk-classified — across an index of 43,000+ MCP servers.