Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.guardway.ai/llms.txt

Use this file to discover all available pages before exploring further.

What this is for

Dashboard → Security summarizes guardrail evaluations and MCP traffic from every attached gateway. Use it to spot bursts of blocks, find the most-triggered policies, and confirm MCP servers are getting the volume you expect. For request and token volume, see Usage. For cost, see Spend. To inspect individual events, open Logs on the relevant gateway.

Options

Time range

Last 24 Hours, Last 7 Days, Last 30 Days. Comparisons against the previous window appear next to each stat.

Filters

  • Gateway — multi-select; leave empty for all attached gateways.

Stat blocks

BlockMetric
Total BlocksRequests blocked by a guardrail in the window.
Total EventsEvery guardrail evaluation (block + warn + redact + log).
MCP RequestsTotal MCP tool calls across all attached servers.
MCP Avg LatencyMean MCP tool-call latency in milliseconds.

Charts and breakdowns

  • Blocks over time — bucketed by the selected range.
  • MCP requests over time — bucketed by the selected range.
  • By severityCritical, High, Medium, Low event counts.
  • Triggered on — top categories that fired (e.g. PII detection, prompt injection, content filter).
  • Event type — top event types observed.
  • Top MCP servers — top 5 servers by request volume.
  • Top MCP tools — top 5 tools by request volume.
If no guardrails fired and no MCP calls flowed in the window, the page shows an empty state instead of charts.

How to configure

This is a read-only analytics view — guardrail policies and MCP servers are configured on Configuration → Security.
Security analytics dashboard
1

Open Dashboard → Security

Open Dashboard → Overview from the dashboard sidebar and click the Security tab.
2

Pick a window and gateways

Set Time range and optionally narrow to specific gateways with the Gateway filter.
3

Drill into a triggered category

Use the Triggered on breakdown to identify which guardrail fired most. Open Logs → Guardrails on the affected gateway to inspect individual evaluations.
4

Tune the policy

If a guardrail is over-firing or under-firing, adjust thresholds and actions on Configuration → Security.