AI agents call list_skills to retrieve information from Memex without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'list_' prefix strongly indicates a data retrieval operation with no side effects. Even without a description, the linguistic pattern classifies this as Read. The low severity reflects that listing available skills poses minimal direct risk—it exposes metadata only, not execution or modification capabilities.
From the tool's definition Tool name 'list_skills' indicates a retrieval/query operation that enumerates skills without modifying state.
Attacks that exploit this kind of access
list_skills. It is categorised as a Read tool in the Memex MCP Server, which means it retrieves data without modifying state.
Register the Memex MCP server in PolicyLayer and add a rule for list_skills: 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 Memex. Nothing to install.
list_skills 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_skills 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_skills. 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_skills is provided by the Memex MCP server (queflyhq/memex). 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 →