Delete a share and withdraw the shared resources.
AI agents call delete_share to permanently remove resources in SAP Business Data Cloud MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a share object and associated shared resources in SAP Business Data Cloud. Deletion of shares cannot be easily undone and directly impacts data access for downstream consumers. This is an irreversible destructive operation affecting business data sharing infrastructure, not a reversible modification.
From the tool's definition Tool name is 'delete_share' and description states 'Delete a share and withdraw the shared resources.' The verb 'delete' combined with 'withdraw' indicates irreversible removal of data sharing configurations and access.
Documented attack patterns abuse exactly the kind of access delete_share gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SAP Business Data Cloud MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_share:
{
"version": "1",
"default": "deny",
"hide": [
"delete_share"
]
} delete_share disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a share and withdraw the shared resources. It is categorised as a Destructive tool in the SAP Business Data Cloud MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the SAP Business Data Cloud MCP Server MCP server in PolicyLayer and add a rule for delete_share: 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 SAP Business Data Cloud MCP Server. Nothing to install.
delete_share is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_share 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 delete_share. 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.
delete_share is provided by the SAP Business Data Cloud MCP Server MCP server (mariodefelipe/sap-bdc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SAP Business Data Cloud MCP Server, 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.
7 SAP Business Data Cloud MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.