Cortex

Listscorecardruleexemptions

listScorecardRuleExemptions

List Scorecard rule exemptions, newest first, with their status, requester, approver and expiry. Filter by Scorecard tag, entity tag, rule identifier, status, requester or approver email, or only exemptions currently in effect; a rule identifier needs a Scorecard tag. Callers who can view Scorecard exemptions see every exemption; other callers see only the exemptions they requested.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	Yes	Page number to return, 0-indexed. Default 0.
`status`	No	Only return exemptions with this status. APPROVED excludes approvals past their end date, which are returned as EXPIRED.
`context`	Yes	Explain why you're invoking this tool now and how its output will be used. Then state how this call supports your overall objective and fits into your broader plan across all tool calls (e.g., why this tool vs. others, and what step it unblocks). Never share any personal details or sensitive information.
`pageSize`	Yes	Number of results to return per page, between 1 and 1000. Default 250.
`entityTag`	No	Only return exemptions for the entity with this tag (`x-cortex-tag`)
`onlyActive`	No	Only return exemptions that are pending, or approved and not yet expired. Default false.
`session_id`	Yes	Session continuity handle, one of two values: the ses_ ID issued for the task underway, or start. This server cannot link your calls between requests on its own, so session continuity travels in this parameter instead. If you were handed a session_id for this task — for example by the agent that spawned you — send that exact value from your first call. Otherwise send start on your first call; the server will issue an opaque correlation ID in the mcp_session field of the result, or in a text block at the start of the result beginning [session_id issued. Then send that exact ses_ value on every later call and hand it to any subagents working the same task. start always begins a new, unrelated task — never send it mid-task. If you send a value this server does not recognize, the result reports it: mcp_session.status of unrecognized, or a text block beginning [session_id unrecognized; re-send the ID issued for this task, or start if none was issued yet. Never invent a ses_ value.
`scorecardTag`	No	Only return exemptions for the Scorecard with this tag
`approverEmail`	No	Only return exemptions approved by the user with this email
`requesterEmail`	No	Only return exemptions requested by the user with this email
`ruleIdentifier`	No	Only return exemptions for the rule with this identifier. Requires `scorecardTag`

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 5, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does disclose meaningful behavior: default sort order, the fields returned, and—most valuably—authorization-scoped results (privileged callers see all exemptions, others see only their own requests). It omits pagination/response-shape behavior, but the schema covers page/pageSize.

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 tight clauses: what it lists, how to filter it, and who sees what. The core purpose is front-loaded with no filler, though the middle filter-enumeration clause is a dense run-on.

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 an 11-parameter read-only listing tool with no output schema or annotations, the description covers output ordering, fields, filtering, the parameter dependency, and access scoping. It leaves pagination semantics to the schema but is otherwise sufficient to call correctly.

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 each parameter is already documented in the schema; the description largely paraphrases those filters. It does reinforce the ruleIdentifier→scorecardTag coupling, but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("List Scorecard rule exemptions") and immediately adds the ordering ("newest first") and the returned fields (status, requester, approver, expiry). No sibling tool lists exemptions, so the resource is unambiguous among the provided siblings.

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

Usage Guidelines4/5

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

It enumerates the filter axes (Scorecard tag, entity tag, rule identifier, status, requester/approver email, active-only) and states the dependency "a rule identifier needs a Scorecard tag", which is actionable usage context. It stops short of any explicit when-not or alternative-tool routing.

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

All Cortex tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?