Check if a specific session is currently active
AI agents call scrappey_session_active to retrieve information from Scrappey MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries the status of a session (active or not), with no side effects. It retrieves read-only status information.
From the tool's definition Check if a specific session is currently active
Attacks that exploit this kind of access
Check if a specific session is currently active. It is categorised as a Read tool in the Scrappey MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Scrappey MCP Server MCP server in PolicyLayer and add a rule for scrappey_session_active: 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 Scrappey MCP Server. Nothing to install.
scrappey_session_active 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 scrappey_session_active 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 scrappey_session_active. 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.
scrappey_session_active is provided by the Scrappey MCP Server MCP server (pim97/mcp-server-scrappey). 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 →