Returns the current session state including active preset ID, load time, and any runtime token overrides. Returns: - activePresetId: Currently loaded preset - loadedAt: When the preset was activated - hasOverrides: Whether runtime overrides are applied - overrideKeys: Top-level override keys
AI agents call get_session_state to retrieve information from UI Preset MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries current session state without side effects. It is a pure read operation that provides visibility into the active UI preset configuration and runtime state. The low severity reflects minimal blast radius if misused—worst case would be information disclosure about the current session configuration, which has no destructive or financial impact.
From the tool's definition Tool returns session state information including activePresetId, loadedAt, hasOverrides, and overrideKeys. The description explicitly states it 'Returns' data with no indication of modification, creation, deletion, or execution of external operations.
Attacks that exploit this kind of access
Returns the current session state including active preset ID, load time, and any runtime token overrides. Returns: - activePresetId: Currently loaded preset - loadedAt: When the preset was activated - hasOverrides: Whether runtime overrides are applied - overrideKeys: Top-level override keys. It is categorised as a Read tool in the UI Preset MCP Server MCP Server, which means it retrieves data without modifying state.
Register the UI Preset MCP Server MCP server in PolicyLayer and add a rule for get_session_state: 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 UI Preset MCP Server. Nothing to install.
get_session_state 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_state 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_state. 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_state is provided by the UI Preset MCP Server MCP server (ncsound919/og-glass). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →