get_conversation_stats

THE RISK

Low Risk

Why get_conversation_stats needs a policy

This tool only retrieves and reports metrics/statistics about existing conversations. It has no side effects, does not execute code, does not modify or delete data, and does not move money. It is a pure read operation with minimal security impact even if abused by an AI agent—at worst, it would expose usage metrics or data structure information about conversations, but cannot alter or destroy anything.

From the tool's definition Tool description states it 'Get[s] detailed statistics' about conversations - a retrieval operation with no modification, deletion, or execution. The terms 'message counts', 'tool usage', 'image counts', and 'file sizes' are all read-only data queries.

Documented attack patterns abuse exactly the kind of access get_conversation_stats gives an agent:

POLICY

How to control get_conversation_stats

PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Code Toolkit, and nothing reaches the server without passing your rules. This is the rule we recommend for get_conversation_stats:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_conversation_stats": {}
  }
}

get_conversation_stats is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Claude Code Toolkit — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Claude Code Toolkit tools

Destructive cleanup_backups Delete old backup files to free up disk space. Destructive wipe_traces Securely wipe ALL Claude Code traces. Overwrites files with zeros before deletion. Require Destructive clean_claude_directory Analyze and clean the .claude directory. Removes debug logs, empty todos, old snapshots, a Destructive clean_traces Selectively clean Claude Code traces by category, age, or project. Destructive enforce_retention Apply data retention policy by deleting sessions older than specified days. Execute run_doctor Full integrity check: detects corrupted JSONL lines, truncated thinking blocks, oversized Execute run_maintenance Run maintenance checks on Claude Code installation. Identifies issues, old backups, and ar Execute start_dashboard Start the web dashboard on a local port. Returns the URL to open in a browser.

All 40 Claude Code Toolkit tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_conversation_stats

What does the get_conversation_stats tool do? +

Get detailed statistics about Claude Code conversations including message counts, tool usage, image counts, and file sizes. It is categorised as a Read tool in the Claude Code Toolkit MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_conversation_stats? +

Register the Claude Code Toolkit MCP server in PolicyLayer and add a rule for get_conversation_stats: 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 Claude Code Toolkit. Nothing to install.

What risk level is get_conversation_stats? +

get_conversation_stats is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_conversation_stats? +

Yes. Add a rate_limit block to the get_conversation_stats 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.

How do I block get_conversation_stats completely? +

Set action: deny in the PolicyLayer policy for get_conversation_stats. 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.

What MCP server provides get_conversation_stats? +

get_conversation_stats is provided by the Claude Code Toolkit MCP server (asifkibria/claude-code-toolkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Claude Code Toolkit tool call.

Start from Claude Code Toolkit, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →