magicblock_health

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

Low RISK CLASS

Category Read

Parameters 00 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/magicblock-health.md

WHAT IT DOES

What magicblock_health does on Sap

AI agents call magicblock_health 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.

RISK

Why magicblock_health is rated Low

Retrieves API health status with no side effects, data modifications, or financial operations.

From the tool's definition Check the health status of the MagicBlock Private Payments API.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

magicblock_health Allowed

magicblock_health 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": {
    "magicblock_health": {}
  }
}

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 magicblock_health call is checked against it from then on.

FAQ

Questions about magicblock_health

What does the magicblock_health tool do? +

Check the health status of the MagicBlock Private Payments API.. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. 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.

How do I enforce a policy on magicblock_health? +

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

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

Can I rate-limit magicblock_health? +

Yes. Add a rate_limit block to the magicblock_health 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 magicblock_health completely? +

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

magicblock_health 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

The MCP Attack Database →

Guides

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