session-get

SERVERDeliberation SOURCEantonbabenko/deliberation

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/deliberation/session-get.md

WHAT IT DOES

What session-get does on Deliberation

AI agents call session-get to retrieve information from Deliberation without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why session-get is rated Low

This is a straightforward retrieval operation that queries stored session records and returns data without side effects. The description confirms it is read-only and does not make external provider calls.

From the tool's definition Tool description explicitly states it 'Fetch[es] a persisted consensus/ask-all session record' and is 'local and read-only (no provider calls)'. Returns session data or error—no modification, deletion, or execution occurs.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs session-get safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Deliberation, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For session-get, this is the rule to start with:

session-get Allowed

session-get is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "session-get": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Deliberation, apply this rule, and every session-get call is checked against it from then on.

FAQ

Questions about session-get

What does the session-get tool do? +

Fetch a persisted consensus/ask-all session record by id (opinions, verdict, arbiter, annotations). Requires sessions.persist; local and read-only (no provider calls). Returns a text-wrapped JSON envelope { session }, or { error } when persistence is off or the id is unknown. It is categorised as a Read tool in the Deliberation MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on session-get? +

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

What risk level is session-get? +

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

Can I rate-limit session-get? +

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

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

session-get is provided by the Deliberation MCP server (antonbabenko/deliberation). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Deliberation, and thousands of servers like it.

This server

All 11 Deliberation tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →