axiorank_update_policyUpdate an existing policy: enable/disable it, rename it, or change its priority. (Other fields are edited in the dashboard.) Requires the policies:write scope.
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | ||
| enabled | No | Arm (true) or disarm (false) the policy. | |
| policyId | Yes | The policy's UUID (from axiorank_list_policies). | |
| priority | No | Lower runs first; ties broken by creation order. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses required scope 'policies:write', which is beyond annotations. Annotations are neutral (no readOnly, no destructive), so description adds auth and field context. No contradictions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with action and scope. No redundant information; every part earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Covers purpose, scope, and updateable fields. No output schema, so missing return value info is acceptable. Could mention if policy object is returned, but overall sufficient for typical use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 75%, and description adds little parameter-level detail beyond what schema already provides. The dashboard note clarifies scope but does not enhance individual parameter understanding significantly.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Describes specific verb 'update' and resource 'policy', lists exactly what can be changed (enable/disable, rename, priority), and distinguishes from siblings like axiorank_create_policy and axiorank_get_policy. The note about dashboard scope clarifies boundaries.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
States when to use (update existing policy) and implies when not (other fields via dashboard). Explicitly lists required scope, but could mention alternatives like create vs. update.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose, covering different aspects of agent, policy, incident, and threat management with no overlap. Tools like axiorank_list_agents and axiorank_get_agent are differentiated by list vs. get, and quarantine vs. revoke serve different use cases.
All tools follow a consistent 'axiorank_verb_noun' pattern in snake_case, making it easy to predict tool names based on action and resource. No mixing of conventions or abbreviations.
With 22 tools, the server covers a comprehensive security governance domain. While slightly above the typical 'well-scoped' range, each tool serves a specific function and the count is justified by the breadth of features (agents, policies, incidents, scoring, verification, audit).
The tool surface covers agent and policy lifecycle (CRUD except delete), incident querying, scoring, verification, and audit. Minor gaps include missing delete operations for policies and incidents, and no way to update incident status. However, the core workflows are well-supported.