End-to-end share provisioning: creates Databricks share, grants to recipient,
AI agents use provision_share to create or update resources in SAP Business Data Cloud MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SAP Business Data Cloud MCP Server environment.
The tool performs reversible write operations (create share, grant permissions) that alter system state and data access configurations. While high-impact due to the security implications of granting data access, it is not destructive (shares/grants can be revoked), not financial, and not arbitrary code execution.
From the tool's definition Tool description states 'creates Databricks share, grants to recipient' — these are create and modify operations that establish new data sharing relationships and permission grants.
Documented attack patterns abuse exactly the kind of access provision_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 provision_share:
{
"version": "1",
"default": "deny",
"tools": {
"provision_share": {
"limits": [
{
"counter": "provision_share_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} provision_share 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.
End-to-end share provisioning: creates Databricks share, grants to recipient,. It is categorised as a Write tool in the SAP Business Data Cloud MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SAP Business Data Cloud MCP Server MCP server in PolicyLayer and add a rule for provision_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.
provision_share 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 provision_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 provision_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.
provision_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.