To search in Spryker documentation by query
AI agents call search_spryker_documentation to retrieve information from Spryker Search Tool MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only search function that retrieves and queries documentation. It has no side effects, cannot modify data, execute code, or cause destructive operations. The blast radius of misuse is minimal—worst case, an AI agent performs excessive searches or retrieves irrelevant documentation. Classification as Read is appropriate.
From the tool's definition Tool performs documentation search by query; returns information from public Spryker documentation without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
To search in Spryker documentation by query. It is categorised as a Read tool in the Spryker Search Tool MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Spryker Search Tool MCP Server MCP server in PolicyLayer and add a rule for search_spryker_documentation: 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 Spryker Search Tool MCP Server. Nothing to install.
search_spryker_documentation 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 search_spryker_documentation 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 search_spryker_documentation. 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.
search_spryker_documentation is provided by the Spryker Search Tool MCP Server MCP server (spryker-community/package-search-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →