To search Spryker documentation path urls by query
AI agents call search_spryker_documentation_path to retrieve information from Spryker Package Search Tool without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool searches and retrieves documentation paths (URLs) based on queries. It is a read-only operation that returns information without side effects—no data modification, code execution, or destructive actions occur. The blast radius of misuse is minimal; an attacker could at worst discover documentation or internal structure details. This is clearly a Read category tool.
From the tool's definition Tool name 'search_spryker_documentation_path' and description 'search Spryker documentation path urls by query' indicate retrieval of documentation URLs without modification or execution.
Attacks that exploit this kind of access
To search Spryker documentation path urls by query. It is categorised as a Read tool in the Spryker Package Search Tool MCP Server, which means it retrieves data without modifying state.
Register the Spryker Package Search Tool MCP server in PolicyLayer and add a rule for search_spryker_documentation_path: 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 Package Search Tool. Nothing to install.
search_spryker_documentation_path 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_path 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_path. 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_path is provided by the Spryker Package Search Tool MCP server (vitaliiivanovspryker/spryker-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 →