AI agents call socheli_list_items to retrieve information from Socheli without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query operation that retrieves metadata about content items (id, status, QA score, title) with optional filtering. It has no capability to modify, delete, create, or execute operations. The blast radius of misuse is minimal—an agent listing items cannot harm data integrity or trigger external actions. This is a classic Read operation.
From the tool's definition Tool name 'socheli_list_items' and description 'List recent content items (id, status, QA score, title). Optionally filter by channel or limit.' indicate retrieval and querying of existing data with no modification, deletion, or execution of side effects.
Attacks that exploit this kind of access
List recent content items (id, status, QA score, title). Optionally filter by channel or limit. It is categorised as a Read tool in the Socheli MCP Server, which means it retrieves data without modifying state.
Register the Socheli MCP server in PolicyLayer and add a rule for socheli_list_items: 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 Socheli. Nothing to install.
socheli_list_items 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 socheli_list_items 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 socheli_list_items. 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.
socheli_list_items is provided by the Socheli MCP server (socheli/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 →