signavio_delete_dictionary_entry

THE RISK

Critical Risk

Why signavio_delete_dictionary_entry needs a policy

The tool permanently removes a dictionary entry from SAP Signavio, which cannot be undone. Dictionary entries are likely business-critical reference data (definitions, metadata, glossary terms). Unauthorized or mistaken deletion could corrupt process documentation and business intelligence across the system. This qualifies as Destructive rather than Write because deletion is irreversible, not merely a modification.

From the tool's definition Tool name explicitly states 'delete' and description confirms 'Delete a dictionary entry' — this is an irreversible deletion operation.

Documented attack patterns abuse exactly the kind of access signavio_delete_dictionary_entry gives an agent:

POLICY

How to control signavio_delete_dictionary_entry

PolicyLayer is an MCP gateway — it sits between your AI agents and Signavio MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for signavio_delete_dictionary_entry:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "signavio_delete_dictionary_entry"
  ]
}

signavio_delete_dictionary_entry disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Signavio MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Signavio MCP Server tools

Destructive signavio_delete_folder Permanently delete a folder and all its contents Write signavio_create_dictionary_category Create a new dictionary category Write signavio_create_dictionary_entry Create a new dictionary entry Write signavio_create_folder Create a new folder Write signavio_create_model Create a new model/diagram Write signavio_move_folder Move a folder to a new parent or to trash Write signavio_move_model Move a model to a different folder Write signavio_publish_model Publish one or more models to Process Collaboration Hub

All 23 Signavio MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Signavio MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about signavio_delete_dictionary_entry

What does the signavio_delete_dictionary_entry tool do? +

Delete a dictionary entry. It is categorised as a Destructive tool in the Signavio MCP Server 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 signavio_delete_dictionary_entry? +

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

What risk level is signavio_delete_dictionary_entry? +

signavio_delete_dictionary_entry 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 signavio_delete_dictionary_entry? +

Yes. Add a rate_limit block to the signavio_delete_dictionary_entry 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 signavio_delete_dictionary_entry completely? +

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

signavio_delete_dictionary_entry is provided by the Signavio MCP Server MCP server (willpowell8/signavio-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Signavio MCP Server tool call.

Start from Signavio MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →