Scan an Appwrite project for over-permissive collection/document permissions. Returns findings JSON with active-probe confirmation. Caches result for use by other tools.
AI agents call audit_project to retrieve information from Appwrite Security without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite the mention of 'active live leak confirmation via anonymous fetch' in the server description, the audit_project tool itself performs reconnaissance and queries existing permissions rather than executing arbitrary code, modifying permissions, or triggering destructive actions.
From the tool's definition Tool description uses 'Scan' and 'Returns findings JSON' — it retrieves and audits permission configuration without modifying Appwrite state.
Attacks that exploit this kind of access
Scan an Appwrite project for over-permissive collection/document permissions. Returns findings JSON with active-probe confirmation. Caches result for use by other tools. It is categorised as a Read tool in the Appwrite Security MCP Server, which means it retrieves data without modifying state.
Register the Appwrite Security MCP server in PolicyLayer and add a rule for audit_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 Appwrite Security. Nothing to install.
audit_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 audit_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 audit_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.
audit_project is provided by the Appwrite Security MCP server (perufitlife/appwrite-security-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 →