List all PAL-registered projects with their configured API services
AI agents call list_projects 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.
The tool performs a read-only query of project metadata. It retrieves and lists existing projects and their configurations with no side effects, data modification, code execution, or irreversible actions. The scope is limited to information about projects within the PAL system itself.
From the tool's definition Tool name is 'list_projects' and description states 'List all PAL-registered projects with their configured API services' — this is a retrieval operation that queries and returns information about existing projects without modifying or executing any…
Attacks that exploit this kind of access
List all PAL-registered projects with their configured API services. 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 list_projects: 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.
list_projects 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 list_projects 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 list_projects. 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.
list_projects 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 →