sap_agent_next_action

SERVERSap SOURCEhttps://mcp.sap.oobeprotocol.ai/mcp

Low RISK CLASS

Category Read

Parameters 60 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/sap-agent-next-action.md

WHAT IT DOES

What sap_agent_next_action does on Sap

AI agents call sap_agent_next_action to retrieve information from Sap without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`intent`	string	—	Current user intent or workflow area.
`toolName`	string	—	Tool that produced the error or partial result, for example sap_register_agent, sap_update_agent, or sap_create_escrow_v2.
`errorCode`	string	—	Machine error code when available, for example hosted_local_signer_required, payment_required, BlockhashNotFound, or expired_or_not_landed.
`errorMessage`	string	—	Human or structured error message returned by the runtime, hosted server, local bridge, or wallet/RPC layer.
`hasSignature`	boolean	—	True when a transaction signature was already produced or submitted. This prevents unsafe duplicate retries.
`paymentRequired`	boolean	—	True when the previous response was an x402/pay.sh payment challenge.

Parameters from the server's own tool schema.

RISK

Why sap_agent_next_action is rated Low

Even though sap_agent_next_action only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs sap_agent_next_action 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_agent_next_action, this is the rule to start with:

sap_agent_next_action Allowed

sap_agent_next_action is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sap_agent_next_action": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sap, apply this rule, and every sap_agent_next_action call is checked against it from then on.

FAQ

Questions about sap_agent_next_action

What does the sap_agent_next_action tool do? +

Free routing resolver for SAP MCP errors and partial results. Use this before retrying after payment_required, hosted_local_signer_required, BlockhashNotFound, missing sap_payments, timeout, or a submitted signature that has not confirmed. SAP MCP execution guidance: Intent: agent bootstrap, routing, skills, or repair guidance. Pricing: free; call directly without x402. Routing: free hosted call; call directly and keep it small/exact when possible. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required. It is categorised as a Read tool in the Sap MCP Server, which means it retrieves data without modifying state.

What parameters does sap_agent_next_action accept? +

sap_agent_next_action accepts 6 parameters: intent, toolName, errorCode, errorMessage, hasSignature, paymentRequired. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on sap_agent_next_action? +

Register the Sap MCP server in PolicyLayer and add a rule for sap_agent_next_action: 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.

What risk level is sap_agent_next_action? +

sap_agent_next_action is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit sap_agent_next_action? +

Yes. Add a rate_limit block to the sap_agent_next_action 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.

How do I block sap_agent_next_action completely? +

Set action: deny in the PolicyLayer policy for sap_agent_next_action. 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.

What MCP server provides sap_agent_next_action? +

sap_agent_next_action 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.

KEEP EXPLORING

More on Sap, and thousands of servers like it.

This server

All 375 Sap tools →

Across the catalogue

get_agent on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →