Skip to main content
Glama
io.github.justrunme/agent-security-contract

io.github.justrunme/agent-security-contract

by justrunme

list_policy_tools

Lists loaded policies, capability catalog, digest, and per-agent tool allowlists from an ASC policy YAML file so you can verify configured tools and rules.

Instructions

List loaded policies and their configured tools/rules.

Returns the capability catalog, capability digest, and per-agent tool allowlists from an ASC policy file.

Args: policy_path: Path to the ASC policy YAML file

Returns: Mapping with version, capability_digest, capabilities, and agents configuration

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": {
      "policy_path": "<policy_path>"
    },
    "name": "list_policy_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
policy_pathYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does establish that this is a read/inspection operation and sketches the returned structure, but it says nothing about failure modes (missing file, malformed YAML), whether policy_path is resolved relative to a working directory, or whether anything is cached or mutated by loading a policy.

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?

Front-loaded verb+resource sentence, followed by Args and Returns sections that are easy to scan. There is minor redundancy between the opening sentence and the Returns block listing capabilities, but nothing is padding.

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?

For a single-parameter read tool with an output schema already present, the description covers purpose, input meaning, and return shape. The remaining gap is operational behavior on error, which is the main thing an agent could still get wrong.

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 0% and the only schema text is the title 'Policy Path', so the description must compensate. It adds that the path points to an ASC policy YAML file, which is genuinely useful, but leaves open whether relative paths are accepted and what file extensions are valid.

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?

The description opens with a specific verb and resource ('List loaded policies and their configured tools/rules') and then enumerates exactly what the output contains (capability catalog, capability digest, per-agent allowlists). This is unambiguous, though it does not explicitly contrast itself with the sibling verification tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this tool versus alternatives, no prerequisites, and no exclusions. The only implied usage is 'when you have an ASC policy file,' which the agent must infer from the parameter name.

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