Agent-Blackbox MCP

driftguard_policy_check

Checks whether a command or path violates Policy as Code rules in driftguard.policy.json or critical-folder protections before execution.

Instructions

Verifica di conformità Policy as Code aziendale: controlla se l'azione o il percorso violano le policy di driftguard.policy.json o protezioni di cartelle critiche.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "actionDescription": "<actionDescription>"
    },
    "name": "driftguard_policy_check"
  }
}

Input Schema

Name	Required	Description	Default
`targetPath`	No	Percorso del file o cartella coinvolto.
`actionDescription`	Yes	Comando o descrizione dell'azione.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv2.0.0Nov 7, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the policy source (driftguard.policy.json, critical folder protections) and that it evaluates an action or path, but it never states that it is a non-destructive read-only check nor what a verdict or violation response looks like.

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?

A single efficient sentence with the core purpose front-loaded and no wasted wording. It could be tightened only slightly, but it is well-sized for a two-parameter check.

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?

For a simple 2-param tool with full schema coverage and no output schema, the description covers what is checked but not the outcome semantics (pass/fail, violation details) an agent would need to act on the result. Adequate but with a clear gap.

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 coverage is 100%, so the two parameters are already documented. The description maps them conceptually (azione -> actionDescription, percorso -> targetPath), but adds no format, syntax, or matching semantics beyond what the schema provides, so baseline 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+resource: a compliance check that determines whether an action or path violates the corporate Policy as Code in driftguard.policy.json or critical-folder protections. An agent can tell this is a validation tool distinct from siblings like driftguard_safety_check or driftguard_dry_run_command, though it never explicitly names an alternative.

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?

Usage is only implied: the agent can infer this should be called to vet an action/path before executing it, but the description gives no explicit when-to-use rule, no prerequisites, and no routing against sibling checks such as safety_check or circuit_breaker_check.

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