To search the Spryker package repository in Github
AI agents call search_spryker_packages 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 retrieves or queries data from a package repository without creating, modifying, deleting, or executing anything. It is a passive read operation with no side effects, fitting the Read category at low severity since the blast radius of misuse is minimal—an attacker could only discover or enumerate packages, not compromise systems or data.
From the tool's definition Tool name is 'search_spryker_packages' and description states it performs 'search' on a GitHub repository. The server description confirms this is a 'natural language search capability' for finding modules and documentation.
Attacks that exploit this kind of access
To search the Spryker package repository in Github. 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_packages: 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_packages 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_packages 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_packages. 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_packages 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 →