Create an alternate key on a Dataverse table (composite supported via key_attributes). Use for race-safe upserts via keyed-PATCH or to enforce a uniqueness constraint that the primary key doesn
AI agents use add_entity_key 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/adds a new alternate key constraint to a Dataverse table. This is a Write operation because it modifies table metadata and schema in a reversible manner (alternate keys can be removed via delete_entity_key). It is not Destructive because the operation is not irreversible—alternate keys can be deleted.
From the tool's definition Tool description states 'Create an alternate key on a Dataverse table' and mentions enabling 'keyed-PATCH' operations for upserts, which are reversible modifications to table schema.
Documented attack patterns abuse exactly the kind of access add_entity_key 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 add_entity_key:
{
"version": "1",
"default": "deny",
"tools": {
"add_entity_key": {
"limits": [
{
"counter": "add_entity_key_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_entity_key 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 an alternate key on a Dataverse table (composite supported via key_attributes). Use for race-safe upserts via keyed-PATCH or to enforce a uniqueness constraint that the primary key doesn. 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 add_entity_key: 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.
add_entity_key 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 add_entity_key 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 add_entity_key. 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.
add_entity_key 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.