AI agents call list_posts to retrieve information from Looba without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and filters existing data (snippet posts) based on search criteria and tags. It performs no modifications, deletions, or external state changes. The operation is inherently non-destructive and aligns with typical Read category patterns (list, search, fetch). The read-only nature of the server reinforces this classification.
From the tool's definition Tool description states 'List Looba snippet posts with optional search, tag filter, and sorting' — a query/listing operation with no data modification. Server description confirms 'read-only access' to the platform.
Attacks that exploit this kind of access
List Looba snippet posts with optional search, tag filter, and sorting. It is categorised as a Read tool in the Looba MCP Server, which means it retrieves data without modifying state.
Register the Looba MCP server in PolicyLayer and add a rule for list_posts: 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 Looba. Nothing to install.
list_posts 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_posts 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_posts. 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_posts is provided by the Looba MCP server (looba-snippet/looba-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 →