AI agents call list_readers to retrieve information from Molmcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to retrieve or enumerate a set of readers from the codebase index. Listing or retrieving data without modification is a Read operation. No destructive, financial, or external execution semantics are evident. Confidence is high despite the empty description because the name and server role (discovery engine) align with passive enumeration.
From the tool's definition Tool name 'list_readers' indicates a listing/retrieval operation. The 'list_*' prefix pattern on MCP servers typically denotes read-only enumeration (see sibling tools like get_command_doc, get_doc_index).
Attacks that exploit this kind of access
list_readers. It is categorised as a Read tool in the Molmcp MCP Server, which means it retrieves data without modifying state.
Register the Mol MCP server in PolicyLayer and add a rule for list_readers: 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 Molmcp. Nothing to install.
list_readers 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_readers 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_readers. 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_readers is provided by the Mol MCP server (molcrafts/molmcp). 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 →