sap_reactivate_tool
Reactivate a SAP tool descriptor by name. SAP MCP context: Direct synapse-sap-sdk wrapper served by this MCP. Read tools return on-chain state; write tools require signer policy, configured RPC, and the active SAP profile. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid v...
This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/sap-reactivate-tool.md
What sap_reactivate_tool does on Sap
AI agents use sap_reactivate_tool to create or update resources in Sap, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sap environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
toolName | string | — | Name of the tool descriptor to reactivate |
Parameters from the server's own tool schema.
Why sap_reactivate_tool is rated Medium
Reactivates a descriptor, reversibly modifying state; write operation with signer policy required.
From the tool's definition Reactivate a SAP tool descriptor by name
Attacks that exploit this kind of access
The rule that runs sap_reactivate_tool safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sap, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sap_reactivate_tool, this is the rule to start with:
sap_reactivate_tool 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Sap, apply this rule, and every sap_reactivate_tool call is checked against it from then on.
Questions about sap_reactivate_tool
Reactivate a SAP tool descriptor by name. SAP MCP context: Direct synapse-sap-sdk wrapper served by this MCP. Read tools return on-chain state; write tools require signer policy, configured RPC, and the active SAP profile. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid value-action; preview cost and transaction effects before user confirmation. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial. It is categorised as a Write tool in the Sap MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
sap_reactivate_tool accepts 1 parameter: toolName. The full parameter table on this page comes from the server's own tool schema.
Register the Sap MCP server in PolicyLayer and add a rule for sap_reactivate_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. Nothing to install.
sap_reactivate_tool 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 sap_reactivate_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 sap_reactivate_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.
sap_reactivate_tool is provided by the Sap MCP server (https://mcp.sap.oobeprotocol.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sap, and thousands of servers like it.
This server
Across the catalogue