Retrieve a list of all CMS collections for a specific Webflow site
AI agents call get_collections to retrieve information from Webflow MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns metadata about CMS collections without modifying, deleting, or executing any operations. It has minimal blast radius—an AI agent misusing it would only expose information about the site's collection structure, not sensitive data within collections or external systems. This is a standard read/query operation.
From the tool's definition The tool description explicitly states 'Retrieve a list of all CMS collections for a specific Webflow site'. The verb 'retrieve' and the nature of listing collections are read-only operations with no data modification.
Attacks that exploit this kind of access
Retrieve a list of all CMS collections for a specific Webflow site. It is categorised as a Read tool in the Webflow MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Webflow MCP Server MCP server in PolicyLayer and add a rule for get_collections: 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 Webflow MCP Server. Nothing to install.
get_collections 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 get_collections 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 get_collections. 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.
get_collections is provided by the Webflow MCP Server MCP server (timkjones/mcp-webflow). 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 →