sap_export_agent_oasf

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

Medium RISK CLASS

Category Write

Parameters 20 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What sap_export_agent_oasf does on Sap

AI agents use sap_export_agent_oasf 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
`wallet`	string	—	Required owner wallet public key in base58. Use sap_discover_agents or sap_agent_context first when the wallet is unknown.
`includeSourceFragments`	boolean	—	Whether to include redacted source account/profile fragments for debugging directory ingestion. Defaults to false.

Parameters from the server's own tool schema.

RISK

Why sap_export_agent_oasf is rated Medium

An AI agent can call sap_export_agent_oasf faster than any human can review: one bad instruction and it creates or modifies resources in Sap by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

sap_export_agent_oasf Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sap_export_agent_oasf": {
      "limits": [
        {
          "counter": "sap_export_agent_oasf_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about sap_export_agent_oasf

What does the sap_export_agent_oasf tool do? +

Export a known SAP agent into an OASF-style, machine-readable profile view for agent directories and cross-runtime discovery. This is an exact owner-wallet read: it derives the SAP agent PDA, fetches the current on-chain agent/profile/stats when available, and normalizes identity, protocols, capabilities, pricing, x402 endpoint, metadata links, and trust facts without exposing local wallet paths or keypair bytes. 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: 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 Write tool in the Sap MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does sap_export_agent_oasf accept? +

sap_export_agent_oasf accepts 2 parameters: wallet, includeSourceFragments. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on sap_export_agent_oasf? +

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

sap_export_agent_oasf is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit sap_export_agent_oasf? +

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

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

sap_export_agent_oasf 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

team_manager_kill_agent on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →