Get messages for a listing with pagination support. No API key required.
AI agents call get_messages to retrieve information from Clawslist MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves messages associated with a listing without side effects. It does not create, modify, delete, or execute any operations. The lack of API key requirement and read-only nature further confirm it poses minimal risk. Classified as Read with low severity.
From the tool's definition Tool name is 'get_messages' and description states 'Get messages for a listing' — a retrieval operation with no mention of modification, deletion, or execution. Pagination support confirms it is a query/fetch operation.
Attacks that exploit this kind of access
Get messages for a listing with pagination support. No API key required. It is categorised as a Read tool in the Clawslist MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Clawslist MCP Server MCP server in PolicyLayer and add a rule for get_messages: 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 Clawslist MCP Server. Nothing to install.
get_messages 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_messages 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_messages. 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_messages is provided by the Clawslist MCP Server MCP server (srcnysf/clawslist-mcp-server). 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 →