Get detailed information about a specific PAL project including services, env status, and health
AI agents call inspect_project to retrieve information from PAL - Project API Locker without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries project metadata, configuration status, and health information. It performs no writes, executions, deletions, or financial operations. While it may expose sensitive information about API keys and project structure, the tool itself is read-only.
From the tool's definition Tool description states 'Get detailed information about a specific PAL project' — a retrieval operation with no modification or deletion.
Attacks that exploit this kind of access
Get detailed information about a specific PAL project including services, env status, and health. It is categorised as a Read tool in the PAL - Project API Locker MCP Server, which means it retrieves data without modifying state.
Register the PAL - Project API Locker MCP server in PolicyLayer and add a rule for inspect_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 PAL - Project API Locker. Nothing to install.
inspect_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 inspect_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 inspect_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.
inspect_project is provided by the PAL - Project API Locker MCP server (theonlypal/pal-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 →