List registered chunking strategies, optionally filtered by content type.
AI agents call list_strategies to retrieve information from ChunkTuner without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays information about existing chunking strategies without creating, modifying, deleting, or executing any operations. It has no side effects and poses minimal risk if called by an AI agent, as it only provides informational data about available configurations.
From the tool's definition Tool name 'list_strategies' combined with description 'List registered chunking strategies' indicates a retrieval operation with no modifications. The optional filtering parameter suggests querying or searching capabilities only.
Attacks that exploit this kind of access
List registered chunking strategies, optionally filtered by content type. It is categorised as a Read tool in the ChunkTuner MCP Server, which means it retrieves data without modifying state.
Register the ChunkTuner MCP server in PolicyLayer and add a rule for list_strategies: 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 ChunkTuner. Nothing to install.
list_strategies 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_strategies 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_strategies. 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_strategies is provided by the ChunkTuner MCP server (shantanu-deshmukh/chunktuner). 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 →