Low Risk

knowledge_stats

Get aggregate knowledge statistics.

How to control knowledge_stats ↓

What knowledge_stats does on Project Tessera

AI agents call knowledge_stats to retrieve information from Project Tessera without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why knowledge_stats needs a policy

This tool retrieves aggregate statistics about stored knowledge, which is a read-only operation. It does not create, modify, delete, execute code, or commit financial operations. The blast radius of misuse is minimal—at worst an agent obtains metadata about indexed documents.

From the tool's definition Tool name is 'knowledge_stats' and description states 'Get aggregate knowledge statistics' — a query operation that retrieves summary data without modification or side effects.

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

How to control knowledge_stats

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "knowledge_stats": {}
  }
}

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

  1. Create a free account and register Project Tessera — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about knowledge_stats

What does the knowledge_stats tool do? +

Get aggregate knowledge statistics. It is categorised as a Read tool in the Project Tessera MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on knowledge_stats? +

Register the Project Tessera MCP server in PolicyLayer and add a rule for knowledge_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 Project Tessera. Nothing to install.

What risk level is knowledge_stats? +

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

Can I rate-limit knowledge_stats? +

Yes. Add a rate_limit block to the knowledge_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 knowledge_stats completely? +

Set action: deny in the PolicyLayer policy for knowledge_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 knowledge_stats? +

knowledge_stats is provided by the Project Tessera MCP server (besslframework-stack/project-tessera). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Project Tessera tool call.

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

Free to start. No card required.

43 Project Tessera tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.