cloudarmor-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLOUDARMOR_PROJECT | Yes | GCP project ID that receives the load-balancer logs | |
| CLOUDARMOR_RULES_INI | No | Path to a rules INI (labels + known-normal priorities) | |
| CLOUDARMOR_HOME_REGION | No | ISO region code treated as home traffic, e.g. JP. Enables the false-positive lens | |
| CLOUDARMOR_BACKEND_SERVICES | No | Comma-separated backend service names to filter (default: all) | all |
| GOOGLE_APPLICATION_CREDENTIALS | Yes | Path to the service-account key file |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| health_checkA | Service health: version, config presence and a minimal API probe. Returns a fixed shape (status/service/version + backend fields) so a monitoring caller never has to branch on missing keys. status is "healthy" when the config loads and a 1-entry probe query succeeds, "degraded" when config loads but the probe fails, "error" when the config itself is unusable. |
| enforce_deniesD | Enforced DENY counts per Cloud Armor rule priority over the window. |
| preview_deniesA | Preview (dry-run) DENY counts per rule priority over the window. A preview rule that stays free of false positives is a candidate for promotion to enforce. |
| home_region_deniesA | Enforced DENYs whose source IP geolocates to the home region. This is the false-positive lens: home-region users being denied on a priority that is not marked known-normal deserves review. Requires CLOUDARMOR_HOME_REGION. |
| daily_briefB | Morning patrol summary: enforced DENYs by rule, home-region false-positive check, and preview DENYs, in one call. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
health_check is clearly distinct. enforce_denies vs preview_denies are differentiated by mode. home_region_denies is a specialized subset of enforced denies, which could be confused with enforce_denies, but the description clarifies its specific lens. daily_brief aggregates the others, but its purpose as a combined summary is evident from the description.
Tool names mix conventions: verb_noun (enforce_denies, preview_denies), noun_verb (health_check), noun_noun (home_region_denies), and adjective_noun (daily_brief). While all are snake_case, the inconsistent verb/noun order and variable parts of speech make naming less predictable.
5 tools is an appropriate scope for a specialized Cloud Armor deny analytics server. The count is neither too sparse to cover the core workflow nor bloated with redundant functionality, and each tool serves a distinct purpose within the defined domain.
The tools cover deny counts (enforced and preview), home-region analysis, and a summary brief, which addresses the primary monitoring workflow. However, there are notable gaps: no way to list or retrieve rule details to map priorities to rule names, and no allow-count or total-traffic metrics. These omissions could require agents to work around the lack of context when analyzing denies.