Fetch all projects from PocketBase. Use this to find project IDs before creating or filtering tasks.
AI agents call list_projects to retrieve information from PocketBase Task MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves project data without modifying, deleting, or executing any operations. It is a read-only query operation used to discover project identifiers. The low severity reflects minimal blast radius—an AI agent could only access project metadata that likely has no financial or destructive implications.
From the tool's definition Tool name 'list_projects' and description 'Fetch all projects from PocketBase' indicates a retrieval operation with no side effects.
Attacks that exploit this kind of access
Fetch all projects from PocketBase. Use this to find project IDs before creating or filtering tasks. It is categorised as a Read tool in the PocketBase Task MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PocketBase Task MCP Server 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 PocketBase Task MCP Server. 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 PocketBase Task MCP Server MCP server (muhammadchhota/mcp-demo). 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 →