Skip to main content
Glama
Sign In
fibx

fibx

Official
by Fibrous-Finance
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Remove a Signing Policy Rule

clear_policy_rule
Destructive

Remove a single rule or the entire local signing policy to control which transactions a wallet will sign. Specify either a rule or all; calls with neither or both are rejected.

Instructions

Remove one rule from the local signing policy with rule, or remove the whole policy with all: true. Removing everything leaves nothing limiting what this wallet will sign. Exactly one of rule or all must be given — a call naming neither or both is rejected.

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": "clear_policy_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
allNoSet to true to remove the whole policy, instead of `rule`
ruleNoThe rule to remove

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.10.2

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false; the description goes further by spelling out the real-world consequence, namely that clearing everything leaves no limit on what the wallet will sign. It stops short of saying whether the policy must then be rebuilt via set_policy_rule or whether any authorization is required.

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?

Three dense sentences, front-loaded with the primary action before the destructive consequence and then the argument constraint. No filler or restatement of the title.

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 two-parameter, no-output-schema mutation tool with strong annotations, the description covers the action, the risk, and the argument rule. Minor omissions are the reversibility path and any permission or auth prerequisites, both of which matter somewhat for an irreversible-seeming security control.

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%, so field meanings are already documented, but the description adds the mutual-exclusivity constraint between `rule` and `all`, which the schema does not enforce with oneOf. That is genuine meaning added beyond the structured fields.

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 names a specific verb (remove) and resource (rule from the local signing policy) and covers both modes: single-rule removal and full-policy removal. This is clearly distinguishable from the siblings get_policy and set_policy_rule.

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 states the selection condition between the two modes and that exactly one of `rule` or `all` is required, including the rejection behavior when neither or both are supplied. It does not explicitly point to set_policy_rule for edits or get_policy for inspection, but the use context is unambiguous.

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

Deploy Server

Other Tools