Get the current status of the SSE subscription connection.
AI agents call get_connection_status to retrieve information from Pikud Haoref Alert System without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only check of an existing connection status. It queries the state of a Server-Sent Events (SSE) subscription and returns that information. There are no side effects, data modifications, code execution, or irreversible actions.
From the tool's definition Tool name 'get_connection_status' and description 'Get the current status of the SSE subscription connection' indicate a query operation that retrieves connection state information without modifying data or triggering external actions.
Attacks that exploit this kind of access
Get the current status of the SSE subscription connection. It is categorised as a Read tool in the Pikud Haoref Alert System MCP Server, which means it retrieves data without modifying state.
Register the Pikud Haoref Alert System MCP server in PolicyLayer and add a rule for get_connection_status: 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 Pikud Haoref Alert System. Nothing to install.
get_connection_status 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 get_connection_status 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 get_connection_status. 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.
get_connection_status is provided by the Pikud Haoref Alert System MCP server (leonmelamud/pikud-a-oref-mcp). 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 →