sap_hermes_recent
Free local tool. Returns recent Hermes Agent sessions for context injection. Use this at session start to recall what the agent worked on recently. If Hermes is not installed, returns empty results. No x402 charge. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: free; call dir...
This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/sap-hermes-recent.md
What sap_hermes_recent does on Sap
AI agents call sap_hermes_recent 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 sessions. Default 3. |
Parameters from the server's own tool schema.
Why sap_hermes_recent is rated Low
Retrieves recent session history data with no side effects or modifications.
From the tool's definition Returns recent Hermes Agent sessions for context injection
Attacks that exploit this kind of access
The rule that runs sap_hermes_recent 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_recent, this is the rule to start with:
sap_hermes_recent is read-only, so it stays allowed. 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_hermes_recent call is checked against it from then on.
Questions about sap_hermes_recent
Free local tool. Returns recent Hermes Agent sessions for context injection. Use this at session start to recall what the agent worked on recently. If Hermes is not installed, returns empty results. No x402 charge. 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 Read tool in the Sap MCP Server, which means it retrieves data without modifying state.
sap_hermes_recent accepts 1 parameter: limit. 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_hermes_recent: 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_hermes_recent is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the sap_hermes_recent 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_hermes_recent. 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_hermes_recent 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