get_session
Get the full results of a previous Meta Council session, including all agent opinions and the synthesis.
This record as markdown: /tools/com-meta-council-decision-intelligence/get-session.md
What get_session does on Meta Council
AI agents call get_session to retrieve information from Meta Council without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
session_id | string | Yes | The session ID to retrieve |
Parameters from the server's own tool schema.
Why get_session is rated Low
This tool retrieves historical session data (opinions and synthesis) without modifying, deleting, executing operations, or committing financial actions. It is a straightforward data retrieval with no blast radius—misuse would expose cached information but cannot alter state or trigger external workflows.
From the tool's definition Tool name 'get_session' and description 'Get the full results of a previous Meta Council session' indicate a retrieval operation with no side effects. The verb 'Get' and the passive framing ('get the results') confirm this is a read-only query.
Attacks that exploit this kind of access
The rule that runs get_session safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Meta Council, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_session, this is the rule to start with:
get_session is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Meta Council, apply this rule, and every get_session call is checked against it from then on.
Questions about get_session
Get the full results of a previous Meta Council session, including all agent opinions and the synthesis. It is categorised as a Read tool in the Meta Council MCP Server, which means it retrieves data without modifying state.
get_session accepts 1 parameter: session_id. Required: session_id. The full parameter table on this page comes from the server's own tool schema.
Register the Meta Council MCP server in PolicyLayer and add a rule for get_session: 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 Meta Council. Nothing to install.
get_session is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_session 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.
Set action: deny in the PolicyLayer policy for get_session. 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.
get_session is provided by the Meta Council MCP server (https://meta-council.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meta Council, and thousands of servers like it.
This server
Across the catalogue