Skip to main content
Glama

BRAINIAC Identity & Access Security

Detect access-policy conflicts

identity-security_access-policy-conflict-detect

Detect conflicting allow/deny access rules from caller-supplied policy exports for the same principal, resource, and action. Price $0.03 USDC. POST /api/v1/identity-security/access-policy-conflict-detect. Unpaid calls return 402 and do not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "identity-security_access-policy-conflict-detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
asOfNo
fileNo
jsonNo
textNo
filesNo
eventsNo
accountsNo
policiesNo
dormantDaysNo
maxTravelKmhNo
mfaPushThresholdNo
mfaWindowMinutesNo
authWindowMinutesNo
sharingWindowHoursNo
serviceBaselineWindowHoursNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description usefully discloses the pricing model ($0.03 USDC), the transport (POST /api/v1/...), and the failure mode (unpaid calls return 402 and do not run) — real behavior beyond structured fields. It says nothing about what the result contains, how conflicts are reported, or what happens when policy exports are malformed or empty, which a mutation-free analysis tool still needs.

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?

Three short sentences with the detection purpose front-loaded, followed by commercial and transport facts; nothing is padded. The endpoint URL is of marginal value to an agent but is contained to a single clause, so the overall structure stays tight.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 16-parameter, deeply nested tool with no annotations and no output schema, the description explains almost none of the input contract or return behavior. It is complete on billing and endpoint but inadequate on how to actually supply policy data and interpret results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 16 parameters including nested file, event, account, and policy objects, so the description must carry the explanatory burden. It only alludes to "policy exports" (gesturing at csv/json/text/file/files) and never mentions asOf, policies, events, accounts, or the numerous threshold parameters like dormantDays and maxTravelKmh. An agent cannot tell which inputs this specific tool actually consumes.

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 uses a specific verb ("Detect") with a precisely scoped resource: "conflicting allow/deny access rules ... for the same principal, resource, and action." That makes the tool's remit distinguishable from siblings such as impossible-travel or mfa-fatigue detection without opening the schema, though it never explicitly contrasts itself with those siblings.

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?

"From caller-supplied policy exports" implies the caller must already hold policy data, which is usable context, and the payment/402 notes tell the agent a call can fail before execution. There is no explicit when-to-use versus alternatives guidance and no statement of what input is required (all 16 parameters are optional).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources