Low Risk

query_events

Query on-chain events by type, sender, package, module, or transaction digest.

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

AI agents call query_events to retrieve information from Sui 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 query_events 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-expertvagabond-sui-mcp-server.yaml
tools:
  query_events:
    rules:
      - action: allow

See the full Sui policy for all 53 tools.

Tool Name query_events
Category Read
MCP Server Sui MCP Server
Risk Level Low

View all 53 tools →

What does the query_events tool do? +

Query on-chain events by type, sender, package, module, or transaction digest.. It is categorised as a Read tool in the Sui MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on query_events? +

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

What risk level is query_events? +

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

Can I rate-limit query_events? +

Yes. Add a rate_limit block to the query_events 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 query_events completely? +

Set action: deny in the Intercept policy for query_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 query_events? +

query_events is provided by the Sui MCP server (sui-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Sui

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.