Skip to main content
Glama

query_security_events

Query Cloudflare security events by zone and time range to retrieve client info, actions, rule details, and bot scores for security event triage.

Instructions

Query security events for a Cloudflare zone using the GraphQL Analytics API. Returns event details including client info, action taken, rule details, bot score, and response status for security event triage.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostNoFilter by requested HTTP hostname
limitNoMax number of events to return (default: 100, max: 10000)
actionNoFilter by action taken: block, challenge, jschallenge, managedchallenge, log, allow, bypass, connectionclose
sourceNoFilter by mitigation source: firewallManaged, firewallCustom, firewallrules, waf, rateLimit, bic, hot, securitylevel, uablock, ip, iprange, asn, country, zonelockdown, l7ddos, botfight, botmanagement, apishield, apishieldschemavalidation, apishieldtokenvalidation, apishieldsequencemitigation, dlp, validation
countryNoFilter by client country name (e.g. US, JP, CN)
date_toYesrequired,End datetime in RFC3339 format
rule_idNoFilter by the rule ID that triggered the event
zone_idYesrequired,The ID of the zone
client_ipNoFilter by client IP address
date_fromYesrequired,Start datetime in RFC3339 format (e.g. 2026-03-23T08:19:58Z)
http_methodNoFilter by HTTP request method (e.g. GET, POST)
request_pathNoFilter by HTTP request path

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the GraphQL Analytics API and states that it returns event details, but does not disclose pagination, default limits, rate limits, data retention, or access requirements. This is minimal transparency for a read operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, each earning its place: the first identifies the operation and API, the second summarizes the return payload. No filler, redundancy, or unnecessary detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 12 parameters and no output schema, the description provides a useful high-level summary of returned fields (client info, action, rule details, bot score, response status) but omits output structure, pagination, and behavioral constraints. Adequate but with clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all 12 parameters are already documented in the schema. The description adds no parameter-specific semantics beyond the return fields, so the baseline score of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Query'), a clear resource ('security events for a Cloudflare zone'), and the underlying API ('GraphQL Analytics API'). It is unambiguous about the operation, though it does not explicitly differentiate from sibling tools like list_security_insights.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'for security event triage' implies a use case and provides some context, but the description offers no explicit guidance on when to use this tool versus alternatives, no exclusions, and no reference to sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.