get_collection_items
AI agents call get_collection_items to retrieve information from SwipeBuilder MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name and naming convention (get_* prefix) combined with the server's stated purpose of retrieving swipes and collections indicates a read-only query operation. No modification, deletion, or execution of external code is implied. Even with an empty description, the consistent pattern of sibling tools and server purpose strongly supports a Read classification with low severity.
From the tool's definition Tool name 'get_collection_items' indicates retrieval operation; sibling tools like 'get_collection', 'get_swipes', and 'get_usage' are all Read operations; server description emphasizes 'retrieve saved ads' and 'monitor API credit usage'.
Attacks that exploit this kind of access
get_collection_items. It is categorised as a Read tool in the SwipeBuilder MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SwipeBuilder MCP Server MCP server in PolicyLayer and add a rule for get_collection_items: 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 SwipeBuilder MCP Server. Nothing to install.
get_collection_items 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_collection_items 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_collection_items. 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_collection_items is provided by the SwipeBuilder MCP Server MCP server (swipebuilder-io/swipebuilder-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 →