To search code in Spryker GitHub repositories
AI agents call search_spryker_package_code 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 tool performs read-only queries across Spryker repositories to retrieve code search results. It retrieves information without side effects, making it a Read category tool. Low severity as it accesses public documentation and packages without the ability to modify, delete, or execute operations. Confidence is high given the clear 'search' semantics and passive nature of the operation.
From the tool's definition Tool name explicitly contains 'search' and description states 'search code in Spryker GitHub repositories' with no modification, deletion, or execution capabilities mentioned. Sibling tools also use 'search_' prefix.
Attacks that exploit this kind of access
To search code in Spryker GitHub repositories. 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_package_code: 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_package_code 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_package_code 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_package_code. 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_package_code 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 →