listDocuments
AI agents call listDocuments to retrieve information from Cloudflare Remote MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'list' prefix strongly indicates this retrieves or queries a collection of documents without side effects. No arguments are visible that would enable modification, deletion, or external execution. The empty description lowers confidence slightly, but the naming convention and sibling tools (readDocument, search) provide contextual clarity that this is a Read operation with minimal blast radius if misused.
From the tool's definition Tool name 'listDocuments' indicates a listing/enumeration operation. Description is empty, but the function name pattern (list*) and sibling context (readDocument, search) suggest data retrieval without modification.
Attacks that exploit this kind of access
listDocuments. It is categorised as a Read tool in the Cloudflare Remote MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Cloudflare Remote MCP Server MCP server in PolicyLayer and add a rule for listDocuments: 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 Cloudflare Remote MCP Server. Nothing to install.
listDocuments 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 listDocuments 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 listDocuments. 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.
listDocuments is provided by the Cloudflare Remote MCP Server MCP server (phkus/craft-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 →