mcp-cloudflare-crunchtools

Get Security Events Tool

get_security_events_tool

Read-only

Retrieve and group Cloudflare security/firewall events by action and source. Pass a zone ID or zone name to inspect activity over a selected date range.

Instructions

Get security/firewall events grouped by action and source.

Provide either zone_id or zone_name, not both.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_security_events_tool"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Number of results (default: 20)
`since`	No	Start date ISO format (default: 30 days ago)
`until`	No	End date ISO format (default: today)
`zone_id`	No	Zone ID (32-character hex string)
`zone_name`	No	Zone name (domain like example.com)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv0.7.2Oct 12, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / limit / description
```
Added value: +"Number of results (default: 20)"
```
- addedInput schema / properties / since / description
```
Added value: +"Start date ISO format (default: 30 days ago)"
```
- addedInput schema / properties / until / description
```
Added value: +"End date ISO format (default: today)"
```
- addedInput schema / properties / zone_id / description
```
Added value: +"Zone ID (32-character hex string)"
```
- addedInput schema / properties / zone_name / description
```
Added value: +"Zone name (domain like example.com)"
```
Changed6 schema fields changedv0.5.1Oct 1, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / limit / description
```
Removed value: -"Number of results (default: 20)"
```
- removedInput schema / properties / since / description
```
Removed value: -"Start date ISO format (default: 30 days ago)"
```
- removedInput schema / properties / until / description
```
Removed value: -"End date ISO format (default: today)"
```
- removedInput schema / properties / zone_id / description
```
Removed value: -"Zone ID (32-character hex string)"
```
- removedInput schema / properties / zone_name / description
```
Removed value: -"Zone name (domain like example.com)"
```
First observedv0.5.0Aug 19, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With readOnlyHint=true already declaring the safety profile, the description adds the aggregation behavior ('grouped by action and source'), which is real value. It does not disclose pagination, default window behavior, or result volume concerns beyond what the schema's defaults imply.

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

Conciseness4/5

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

Two short sentences with the core action front-loaded and the constraint immediately following. Nothing is wasted, though it is terse enough that some helpful context is omitted.

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

Completeness4/5

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

Return values are covered by the output schema and all five parameters are documented at 100% coverage, so the description doesn't need to explain them. It is complete enough to call correctly, with only marginal gaps around which sibling to choose.

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

Parameters4/5

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

Schema coverage is already 100%, setting a baseline of 3. The description goes beyond the schema by stating that zone_id and zone_name are mutually exclusive, an XOR constraint the schema cannot express, which meaningfully guides invocation.

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 ('Get') and resource ('security/firewall events') and adds that results are 'grouped by action and source', which tells the agent the shape of the output. It does not, however, differentiate itself from nearby analytics tools like get_zone_analytics_tool or get_top_pages_tool, so the boundary between siblings is left implicit.

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 description supplies one clear usage rule ('Provide either zone_id or zone_name, not both'), which is genuinely helpful mutual-exclusion guidance. It offers no when-to-use context relative to the other analytics/security siblings, so an agent must infer when this tool is preferred over them.

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

Deploy Server