This record as markdown: /tools/frontmcp/check-session.md
What check-session does on Frontmcp
AI agents call check-session to retrieve information from Frontmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why check-session is rated Low
This is a pure information retrieval tool. It checks and returns session state without side effects. No data is created, modified, deleted, or executed. The blast radius of misuse is minimal—an agent could only read session information it likely already has access to.
From the tool's definition Tool name 'check-session' and description 'Check current session and retrieve state' indicate a query operation that retrieves information about the current session without modifying, executing external operations, or affecting data.
Attacks that exploit this kind of access
The rule that runs check-session safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Frontmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check-session, this is the rule to start with:
check-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 Frontmcp, apply this rule, and every check-session call is checked against it from then on.
Questions about check-session
Check current session and retrieve state. It is categorised as a Read tool in the Frontmcp MCP Server, which means it retrieves data without modifying state.
Register the Front MCP server in PolicyLayer and add a rule for check-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 Frontmcp. Nothing to install.
check-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 check-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 check-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.
check-session is provided by the Front MCP server (agentfront/frontmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Front, and thousands of servers like it.
This server
Across the catalogue