list_libraries
List the libraries search_dev_stack has docs for (${names}), each with its slug, name, source, and description. Use it to check coverage or to get a \
This record as markdown: /tools/cloudflare/list-libraries.md
What list_libraries does on Cloudflare
AI agents call list_libraries to retrieve information from Cloudflare without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_libraries is rated Low
This is a straightforward informational lookup tool that queries documentation coverage for libraries. It has no side effects, creates no data, executes no code, and makes no destructive or financial changes. It falls squarely into the Read category with low severity since misuse would only expose informational content about available libraries.
From the tool's definition The tool 'list_libraries' retrieves and lists available libraries with their metadata (slug, name, source, description). The verb 'List' and the phrase 'get a' indicate a read-only query operation with no modification of state.
Attacks that exploit this kind of access
The rule that runs list_libraries safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Cloudflare, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_libraries, this is the rule to start with:
list_libraries is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Cloudflare, apply this rule, and every list_libraries call is checked against it from then on.
Questions about list_libraries
List the libraries search_dev_stack has docs for (${names}), each with its slug, name, source, and description. Use it to check coverage or to get a \. It is categorised as a Read tool in the Cloudflare MCP Server, which means it retrieves data without modifying state.
Register the Cloudflare MCP server in PolicyLayer and add a rule for list_libraries: 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. Nothing to install.
list_libraries 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_libraries 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_libraries. 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_libraries is provided by the Cloudflare MCP server (https://builds.mcp.cloudflare.com/sse). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Cloudflare, and thousands of servers like it.
This server
Across the catalogue