protected_tool
A other tool on the Sap Btp Destination MCP server.
This record as markdown: /tools/facusada-mcp-btp/protected-tool.md
What protected_tool does on Sap Btp Destination
AI agents call protected_tool as a supporting operation in Sap Btp Destination workflows.
Why protected_tool is rated Low
With no description and only a vague name, there is insufficient information to classify this tool into a meaningful risk category. The name 'protected_tool' does not clearly indicate read, write, execute, destructive, or financial operations. Confidence is very low due to the lack of evidence.
From the tool's definition Tool name is 'protected_tool' with empty description. No functional information is available.
Attacks that exploit this kind of access
The rule that runs protected_tool safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sap Btp Destination, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For protected_tool, this is the rule to start with:
protected_tool gets a rate cap, and everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Sap Btp Destination, apply this rule, and every protected_tool call is checked against it from then on.
Questions about protected_tool
protected_tool is a other tool on the Sap Btp Destination MCP server. It is categorised as a Other tool in the Sap Btp Destination MCP Server, which means it performs auxiliary operations.
Register the Sap Btp Destination MCP server in PolicyLayer and add a rule for protected_tool: 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 Btp Destination. Nothing to install.
protected_tool is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the protected_tool 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 protected_tool. 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.
protected_tool is provided by the Sap Btp Destination MCP server (facusada/mcp-btp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sap Btp Destination, and thousands of servers like it.
This server
Across the catalogue