AI agents call auth_check 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.
auth_check queries local configuration to verify authentication status and retrieve metadata. It has no side effects, creates no changes, executes no operations, and poses minimal risk if misused by an agent (at worst, it leaks non-sensitive configuration details like project_id or base_url already visible to an authenticated context). This is a Read operation.
From the tool's definition The tool description states it 'Report[s] whether ~/.config/shipeasy/config.json holds a valid CLI token' and 'Returns { authenticated, project_id, base_url, user_email }'.
Attacks that exploit this kind of access
Report whether ~/.config/shipeasy/config.json holds a valid CLI token. Returns { authenticated, project_id, base_url, user_email }. 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 auth_check: 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.
auth_check 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 auth_check 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 auth_check. 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.
auth_check 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 →