Monitoring coverage
Where your monitoring stands — how many tests are enabled, how many pass, fail or error, how long anything has been failing, and which check types account for the failures.
| Plugin | Area | Access |
|---|---|---|
| drata-grc-skills | Compliance & Audit Readiness | Read-only |
Purpose
- Reports test status, enabled against disabled.
- Reports results as passed, failed and errored, scoped to Production so the numbers match the Drata UI.
- Shows how long tests have been failing, and failures grouped by check type.
Access: This skill cannot change anything in Drata.
MCP tools used
| MCP tool | Level | OAuth scope |
|---|---|---|
| Get Company | Read | read:company |
| Search Monitoring Tests | Read | read:monitor-test |
This skill uses every scope listed above; without them it fails partway through. What any tool returns is bounded by your Drata role as well as the scope — see MCP Server setup.
Run it
/plugin marketplace add drata/drata-claude-plugin
/plugin install drata-grc-skills@drataThen run the skill by name:
/drata-grc-skills:drata-monitoring-reportOr ask for it in your own words:
- "monitoring coverage"
- "how many tests are failing"
Before you start
- Connect the Drata MCP server. See MCP Server setup.
- Your MCP OAuth configuration must grant the scopes behind the tools listed above.
Related skills
- Controls needing work — Two worklists over your not-ready controls — the ones with nothing mapped, and the ones whose manual evidence is out of date — plus any control missing an owner or a description.