AI agents call check_session to retrieve information from Reddirect without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a status check and returns authentication state (username or anonymous status). It is purely informational with no side effects, data modification, or external operations triggered. It falls squarely into the Read category. Severity is low because the information exposed (username or anonymous status) is non-sensitive and poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'check_session' and description 'Check if connected to a Reddit account. Shows username if authorized, or anonymous if not.' indicate a read-only operation that retrieves session status information without modifying, executing external operations,…
Attacks that exploit this kind of access
Check if connected to a Reddit account. Shows username if authorized, or anonymous if not. Run. It is categorised as a Read tool in the Reddirect MCP Server, which means it retrieves data without modifying state.
Register the Reddirect 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 Reddirect. 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 Reddirect MCP server (jeebus87/reddirect). 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 →