sse_get_events

Get captured SSE events with filters and pagination.

SERVERJshookmcp SOURCE@jshookmcp/jshook

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-vmoranv-jshookmcp/sse-get-events.md

WHAT IT DOES

What sse_get_events does on Jshookmcp

AI agents call sse_get_events to retrieve information from Jshookmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why sse_get_events is rated Low

Retrieves previously captured Server-Sent Events data; no side effects or modifications occur.

From the tool's definition Get captured SSE events with filters and pagination.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs sse_get_events safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Jshookmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sse_get_events, this is the rule to start with:

sse_get_events Allowed

sse_get_events is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sse_get_events": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Jshookmcp, apply this rule, and every sse_get_events call is checked against it from then on.

FAQ

Questions about sse_get_events

What does the sse_get_events tool do? +

Get captured SSE events with filters and pagination. It is categorised as a Read tool in the Jshookmcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on sse_get_events? +

Register the Jshook MCP server in PolicyLayer and add a rule for sse_get_events: 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 Jshookmcp. Nothing to install.

What risk level is sse_get_events? +

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

Can I rate-limit sse_get_events? +

Yes. Add a rate_limit block to the sse_get_events 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.

How do I block sse_get_events completely? +

Set action: deny in the PolicyLayer policy for sse_get_events. 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 sse_get_events? +

sse_get_events is provided by the Jshook MCP server (@jshookmcp/jshook). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Jshook, and thousands of servers like it.

This server

All 736 Jshook tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →