Critical Risk →

dataset_mutate

Mutate dataset records (create/update/delete)

Part of the ExecuFunction server.

dataset_mutate can permanently delete data in ExecuFunction, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE EXECUFUNCTION →

Free to start. No card required.

AI agents may call dataset_mutate to permanently remove or destroy resources in ExecuFunction. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call dataset_mutate in a loop, permanently destroying resources in ExecuFunction. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "dataset_mutate"
  ]
}

See the full ExecuFunction policy for all 77 tools.

Get this rule live on your own ExecuFunction server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY EXECUFUNCTION →

View all 77 tools →

These attack patterns abuse exactly the kind of access dataset_mutate gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so dataset_mutate only ever does what you allow.

SECURE EXECUFUNCTION →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the dataset_mutate tool do? +

Mutate dataset records (create/update/delete). It is categorised as a Destructive tool in the ExecuFunction MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on dataset_mutate? +

Register the ExecuFunction MCP server in PolicyLayer and add a rule for dataset_mutate: 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 ExecuFunction. Nothing to install.

What risk level is dataset_mutate? +

dataset_mutate is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit dataset_mutate? +

Yes. Add a rate_limit block to the dataset_mutate 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.

How do I block dataset_mutate completely? +

Set action: deny in the PolicyLayer policy for dataset_mutate. 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.

What MCP server provides dataset_mutate? +

dataset_mutate is provided by the ExecuFunction MCP server (@execufunction/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every ExecuFunction tool call.

Deterministic rules across all 77 ExecuFunction tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.