get_knowledge_stats

THE RISK

Low Risk

Why get_knowledge_stats needs a policy

This tool retrieves and returns statistics about the knowledge base (likely counts, sizes, or metadata summaries). It has no side effects, does not execute code, does not modify data, and does not delete anything. It is a straightforward query operation that only reads and returns information.

From the tool's definition Tool name 'get_knowledge_stats' and description 'Get statistics about your personal knowledge base' indicate retrieval of aggregate information without modification or deletion. Statistics gathering is a read-only operation.

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

POLICY

How to control get_knowledge_stats

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

policy.json

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

get_knowledge_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 Opencode Personal Knowledge — 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 Opencode Personal Knowledge tools

Destructive delete_knowledge Delete a knowledge entry from the database Write start_logging_session Start logging a new session for later search. IMPORTANT: After starting, you MUST call log Write end_session End the current or specified session Write log_message Log a message to the current session. REQUIRED: Call this for EVERY user message and agent Write store_knowledge Store a new knowledge entry in your personal knowledge base. Use this to save important in Write update_knowledge Update an existing knowledge entry Read get_knowledge Get a specific knowledge entry by its ID Read get_session Get details and messages from a specific session

All 15 Opencode Personal Knowledge 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_knowledge_stats

What does the get_knowledge_stats tool do? +

Get statistics about your personal knowledge base. It is categorised as a Read tool in the Opencode Personal Knowledge MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_knowledge_stats? +

Register the Opencode Personal Knowledge MCP server in PolicyLayer and add a rule for get_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 Opencode Personal Knowledge. Nothing to install.

What risk level is get_knowledge_stats? +

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

Can I rate-limit get_knowledge_stats? +

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

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

get_knowledge_stats is provided by the Opencode Personal Knowledge MCP server (nocturnlabs/opencode-personal-knowledge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Opencode Personal Knowledge tool call.

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

CHECK YOUR STACK →