magicsword-mcp

Official

by magicsword-io

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

Flip a policy from audit to enforcing

flip_to_enforcing

Destructive

Instructions

Promotes a MagicSword policy from audit to enforcing mode through the Portal server confirmation flow. First call without confirmation_token to get readiness, blockers, endpoint count, and a one-time token. Show the preview to the human. Second call with confirmation_token to commit. Requires policies:write. This is two-step API confirmation, not MFA: the same API key can perform both calls. Human approval must be obtained by the MCP host.

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_id": "<policy_id>"
    },
    "name": "flip_to_enforcing"
  }
}

Input Schema

Name	Required	Description
`policy_id`	Yes	Policy UUID to flip
`confirmation_token`	No	Token returned by the preview call. Passing this commits enforcement.
`acknowledge_blockers`	No	Set true only when the human explicitly accepts preview blockers. Used on the preview call.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Oct 15, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already mark the operation as destructive, non-idempotent, and write-scoped. The description adds important behavioral context beyond annotations: the two-call confirmation flow, the policies:write requirement, clarification that this is not MFA, and the host-side human approval obligation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the purpose, then explains the two-step flow and human approval requirement. Every sentence adds operational value, and there is no filler.

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

Completeness5/5

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

Although there is no output schema, the description explains what the preview call returns: readiness, blockers, endpoint count, and a one-time token. It also explains the commit path and human approval responsibility, making the definition complete for correct invocation.

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

Parameters4/5

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

Schema coverage is 100%, and the schema itself documents all three parameters. The description adds flow-level semantics beyond the schema by explaining that confirmation_token commits enforcement on the second call and acknowledge_blockers is used on the preview call.

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?

The description states a specific verb and resource: promoting a MagicSword policy from audit to enforcing mode through the Portal server confirmation flow. It clearly distinguishes the tool from siblings like show_policy, manage_policy_rules, and apply_policy_to_endpoints.

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

Usage Guidelines5/5

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

The two-step usage is explicit: first call without confirmation_token to preview readiness, then call with confirmation_token to commit. It also states that human approval must be obtained by the MCP host and when acknowledge_blockers applies.

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