Skip to main content
Glama
Sign In
appwrite-security-mcp

appwrite-security-mcp

by Perufitlife
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

audit_project

Scan an Appwrite project for over-permissive permissions and receive a JSON report with live confirmation of leaks.

Instructions

Scan an Appwrite project for over-permissive collection/document permissions. Returns findings JSON with active-probe confirmation. Caches result for use by other tools.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "audit_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
endpointNoAppwrite endpoint base URL, e.g. https://cloud.appwrite.io/v1. Optional if APPWRITE_ENDPOINT env var is set.
projectNoAppwrite project ID. Optional if APPWRITE_PROJECT_ID is set.
keyNoAppwrite server API key with scopes: databases.read, collections.read. Optional if APPWRITE_API_KEY is set.
no_probeNoSkip the live anonymous probe.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description must disclose behavioral traits. It notes the return format (findings JSON), live probe confirmation, and caching behavior. However, it does not specify if the scan is read-only, any required permissions, or potential impacts, leaving some transparency gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise with two sentences. The first sentence states the core action, and the second adds key behavioral details (return format and caching). No unnecessary words, well-suited for quick reading.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (4 parameters, no output schema), the description covers the tool's purpose and caching but lacks details on the findings JSON structure, the meaning of 'active-probe confirmation', or how the cached result is used by other tools. There is room for improvement in explaining the output.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so each parameter is already documented. The description adds value by indicating that 'endpoint', 'project', and 'key' are optional if corresponding env vars are set. This is helpful but does not substantially expand meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: scanning Appwrite projects for over-permissive permissions. It uses specific verbs and resources ('scan', 'Appwrite project', 'over-permissive collection/document permissions') and distinguishes itself from sibling tools like 'list_findings' and 'preview_fix' by being the initial scanning step.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context by mentioning caching for other tools, suggesting this is a preparatory step. However, it does not explicitly state when to use this tool versus alternatives like 'list_findings' or 'preview_fix', nor does it provide conditions for not using it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools