list_sessions

THE RISK

Low Risk

Why list_sessions needs a policy

Listing sessions queries existing data without creating, modifying, deleting, or executing operations. This is a standard Read operation with minimal security risk unless session data itself is sensitive, but listing metadata is typically low-severity.

From the tool's definition Tool name is 'list_sessions' and description states 'List chat sessions' — this is a retrieval operation with no modification or side effects.

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

POLICY

How to control list_sessions

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

policy.json

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

list_sessions 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 WeKnora MCP Server — 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 WeKnora MCP Server tools

Destructive delete_chunk Delete a chunk Destructive delete_knowledge Delete knowledge Destructive delete_knowledge_base Delete a knowledge base Destructive delete_session Delete a session Execute chat Send a chat message to a session Write create_knowledge_base Create a new knowledge base Write create_knowledge_from_url Create knowledge from URL Write create_model Create a new model

All 21 WeKnora MCP Server 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 list_sessions

What does the list_sessions tool do? +

List chat sessions. It is categorised as a Read tool in the WeKnora MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_sessions? +

Register the WeKnora MCP Server MCP server in PolicyLayer and add a rule for list_sessions: 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 WeKnora MCP Server. Nothing to install.

What risk level is list_sessions? +

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

Can I rate-limit list_sessions? +

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

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

list_sessions is provided by the WeKnora MCP Server MCP server (nannaolympicbroadcast/weknoramcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every WeKnora MCP Server tool call.

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

CHECK YOUR STACK →