4 tools. 2 can modify or destroy data without limits.
2 write tools that can modify data. Rate limits recommended.
Last updated:
Write operations (mdk-create, mdk-manage) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.
Intercept sits between your agent and Mdk. Every tool call checked against your policy before it executes — so your agent can do its job without breaking things.
npx -y @policylayer/intercept scan -- npx -y @sap/mdk-mcp-server mdk-create:
rules:
- rate_limit: 30/hour Prevents bulk unintended modifications from agents caught in loops.
mdk-docs:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
The Mdk server has 2 write tools including mdk-create, mdk-manage. Set rate limits in your policy file -- for example, rate_limit: 10/hour prevents an agent from making more than 10 modifications per hour. Intercept enforces this at the transport layer.
4 tools across 2 categories: Read, Write. 2 are read-only. 2 can modify, create, or delete data.
One line change. Instead of running the Mdk server directly, prefix it with Intercept: intercept -c io-github-sap-mdk-mcp-server.yaml -- npx -y @@sap/mdk-mcp-server. Download a pre-built policy from policylayer.com/policies/io-github-sap-mdk-mcp-server and adjust the limits to match your use case.
Set budgets, approvals, and hard limits across MCP servers.
npx -y @policylayer/intercept init