event_status

Check if real-time event monitoring is active.

SERVERIconnect SOURCEiconnect-mcp

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-heznpc-iconnect/event-status.md

WHAT IT DOES

What event_status does on Iconnect

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

RISK

Why event_status is rated Low

This tool retrieves the current state of event monitoring (a read operation). It queries information without side effects, creating no data modifications, code execution, or destructive actions. The low severity reflects minimal risk even if misused—an agent could only discover whether monitoring is enabled, posing no blast radius to user data or system integrity.

From the tool's definition Tool name 'event_status' and description 'Check if real-time event monitoring is active' indicate a status query operation with no modification or execution of actions.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs event_status safely

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

event_status Allowed

event_status 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": {
    "event_status": {}
  }
}

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

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

FAQ

Questions about event_status

What does the event_status tool do? +

Check if real-time event monitoring is active. It is categorised as a Read tool in the Iconnect MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on event_status? +

Register the Iconnect MCP server in PolicyLayer and add a rule for event_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 Iconnect. Nothing to install.

What risk level is event_status? +

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

Can I rate-limit event_status? +

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

How do I block event_status completely? +

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

What MCP server provides event_status? +

event_status is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Iconnect, and thousands of servers like it.

This server

All 279 Iconnect tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server →get_event_details on CTFtime MCP Server → The MCP Attack Database →

Guides

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