AI agents call detect_project to retrieve information from Shipeasy without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool only reads and reports on the current project configuration and SDK installation state. It does not modify files, execute code, trigger external operations, or delete anything. The action of inspecting a directory and returning metadata is purely informational, fitting the Read category. Severity is low because misuse would only expose benign project metadata to the AI agent.
From the tool's definition Tool performs inspection and returns data about the working directory: 'Inspect the working directory and return language, framework, package manager, shipeasy SDK install state (experimentation + i18n), and loader-script presence.' This is a pure retrieval…
Attacks that exploit this kind of access
Inspect the working directory and return language, framework, package manager, shipeasy SDK install state (experimentation + i18n), and loader-script presence. It is categorised as a Read tool in the Shipeasy MCP Server, which means it retrieves data without modifying state.
Register the Shipeasy MCP server in PolicyLayer and add a rule for detect_project: 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 Shipeasy. Nothing to install.
detect_project 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 detect_project 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 detect_project. 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.
detect_project is provided by the Shipeasy MCP server (shipeasy-ai/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 →