session-info
Get information about the current transport session
This record as markdown: /tools/frontmcp/session-info.md
What session-info does on Frontmcp
AI agents call session-info 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 session-info is rated Low
This tool retrieves metadata about the current session without creating, modifying, deleting, or executing any operations. It is a simple informational query that has no blast radius if misused by an AI agent—the worst outcome would be leaking session details that may already be available to the agent in context.
From the tool's definition Tool name 'session-info' and description 'Get information about the current transport session' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs session-info 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 session-info, this is the rule to start with:
session-info 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 session-info call is checked against it from then on.
Questions about session-info
Get information about the current transport session. 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 session-info: 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.
session-info 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 session-info 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 session-info. 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.
session-info 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