sap_hermes_search

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

Low RISK CLASS

Category Read

Parameters 21 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-hermes-search.md

WHAT IT DOES

What sap_hermes_search does on Sap

AI agents call sap_hermes_search 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
`limit`	number	—	Max results. Default 5.
`query`	string	Yes	Natural language search query.

Parameters from the server's own tool schema.

RISK

Why sap_hermes_search is rated Low

Tool retrieves historical conversation data with no modification, deletion, or external effects.

From the tool's definition Searches session history for conversations. Enables cross-session context recall.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

sap_hermes_search Allowed

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

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

FAQ

Questions about sap_hermes_search

What does the sap_hermes_search tool do? +

Free local tool. Searches Hermes Agent session history for relevant past conversations. Enables cross-session context recall. If Hermes is not installed, returns empty results. No x402 charge. SAP MCP execution guidance: Intent: read/discovery 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 Read tool in the Sap MCP Server, which means it retrieves data without modifying state.

What parameters does sap_hermes_search accept? +

sap_hermes_search accepts 2 parameters: limit, query. Required: query. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on sap_hermes_search? +

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

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

Can I rate-limit sap_hermes_search? +

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

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

sap_hermes_search 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

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →hybrid_search on Azure AI Agent Service + Azure AI Search MCP Server → The MCP Attack Database →

Guides

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