Add a column (attribute) to an existing Dataverse table
AI agents use add_attribute 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 a new attribute (column) in a Dataverse table, which is a reversible schema modification. It qualifies as Write rather than Destructive because attributes can be removed (via the sibling tool 'delete_attribute').
From the tool's definition Tool name 'add_attribute' and description 'Add a column (attribute) to an existing Dataverse table' indicate creation/modification of table schema structure.
Documented attack patterns abuse exactly the kind of access add_attribute 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_attribute:
{
"version": "1",
"default": "deny",
"tools": {
"add_attribute": {
"limits": [
{
"counter": "add_attribute_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_attribute 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.
Add a column (attribute) to an existing 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 add_attribute: 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_attribute 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_attribute 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_attribute. 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_attribute 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.