New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

sap_find_tools_by_category

Find on-chain tool descriptors by SDK tool category name or numeric category. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program. Use these reads to inspect current chain state before mutating registry, payment, reputation, memory, or tool accounts. SAP M...

SERVERSap SOURCEhttps://mcp.sap.oobeprotocol.ai/mcp
Low RISK CLASS
Category Read
Parameters 30 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-find-tools-by-category.md

What sap_find_tools_by_category does on Sap

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

ParameterTypeRequiredDescription
limit number Maximum number of tools to return (default: 50)
hydrate boolean Whether to include full hydrated tool descriptors in results (default: true)
category string | number Tool category name (e.g. "defi", "infrastructure") or numeric category ID

Parameters from the server's own tool schema.

Why sap_find_tools_by_category is rated Low

Queries Solana chain state for tool metadata without modification or execution capabilities.

From the tool's definition Find on-chain tool descriptors; Read-only SAP SDK wrapper; inspect current chain state.

Questions about sap_find_tools_by_category

What does the sap_find_tools_by_category tool do? +

Find on-chain tool descriptors by SDK tool category name or numeric category. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program. Use these reads to inspect current chain state before mutating registry, payment, reputation, memory, or tool accounts. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: priced by hosted x402 challenge. 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.

What parameters does sap_find_tools_by_category accept? +

sap_find_tools_by_category accepts 3 parameters: limit, hydrate, category. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on sap_find_tools_by_category? +

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

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

Can I rate-limit sap_find_tools_by_category? +

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

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

sap_find_tools_by_category 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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Sap's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.