Full context for an AI session: every decision and every intervention, ordered chronologically. Use to recap what happened in a long-running session.
AI agents call get_session_context to retrieve information from Carto MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns session history data without creating, modifying, deleting, or executing operations. It is purely informational retrieval, fitting the Read category for tools that retrieve or query data with no side effects. Severity is low because session context is metadata about prior AI decisions, not sensitive operational data or system-critical information.
From the tool's definition Tool description states it retrieves 'full context for an AI session' and 'every decision and every intervention, ordered chronologically.' The verb 'get' and action 'recap what happened' indicate data retrieval with no modification or side effects.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access get_session_context gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Carto MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_session_context:
{
"version": "1",
"default": "deny",
"tools": {
"get_session_context": {}
}
}get_session_context is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Full context for an AI session: every decision and every intervention, ordered chronologically. Use to recap what happened in a long-running session. It is categorised as a Read tool in the Carto MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Carto MCP Server MCP server in PolicyLayer and add a rule for get_session_context: 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 Carto MCP Server. Nothing to install.
get_session_context 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_context 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_context. 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_context is provided by the Carto MCP Server MCP server (theanshsonkar/carto). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 22 Carto MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
22 Carto MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.