list_skills
AI agents call list_skills to retrieve information from Cartesi Knowledge 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 or enumerates skills (likely documentation, guides, or resources) from the Cartesi knowledge base. It performs a query operation returning data without modification, deletion, or execution of external code. The confidence is slightly lowered due to the missing tool description, but the server's read-only nature and naming convention provide strong context.
From the tool's definition Tool name 'list_skills' is a list operation, consistent with sibling tools (all prefixed with 'get_', 'fetch_', 'build_', or 'identify_') that retrieve read-only knowledge and documentation. Server description emphasizes 'read-only knowledge access'.
Attacks that exploit this kind of access
list_skills. It is categorised as a Read tool in the Cartesi Knowledge MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Cartesi Knowledge MCP Server 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 Cartesi Knowledge MCP Server. 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 Cartesi Knowledge MCP Server MCP server (mugen-builders/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 →