Low Risk

session_end

session_end

Part of the Looking Glass MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call session_end to retrieve information from Looking Glass without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though session_end only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

io-github-sahib-sawhney-wh-looking-glass-mcp.yaml
tools:
  session_end:
    rules:
      - action: allow

See the full Looking Glass policy for all 71 tools.

Tool Name session_end
Category Read
Risk Level Low

View all 71 tools →

Agents calling read-class tools like session_end have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the session_end tool do? +

session_end. It is categorised as a Read tool in the Looking Glass MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on session_end? +

Add a rule in your Intercept YAML policy under the tools section for session_end. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Looking Glass MCP server.

What risk level is session_end? +

session_end is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit session_end? +

Yes. Add a rate_limit block to the session_end rule in your Intercept 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.

How do I block session_end completely? +

Set action: deny in the Intercept policy for session_end. 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.

What MCP server provides session_end? +

session_end is provided by the Looking Glass MCP server (looking-glass-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Looking Glass

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.