Skip to main content
Glama
Sign In
fibx

fibx

Official
by Fibrous-Finance
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Set a Signing Policy Rule

set_policy_rule
Destructive

Configure one local signing-policy rule to restrict transaction expiry, allowed chains, per-chain native value caps, or token destinations before signing.

Instructions

Set one rule on the local signing policy. Rules: expiry, allowedChains, .maxValue, .allowedDestinations. Lists are comma-separated. maxValue caps the native value of one transaction and does not bound token amounts — an ERC-20 transfer carries value 0 — so use allowedDestinations to bound where tokens may go.

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": {
      "rule": "<rule>",
      "value": "<value>"
    },
    "name": "set_policy_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
ruleYesexpiry, allowedChains, <chain>.maxValue or <chain>.allowedDestinations
valueYesThe value; comma-separated for lists

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.10.2

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation risk is known. The description adds genuinely useful domain semantics about maxValue not bounding ERC-20 transfers, but it does not say whether setting a rule overwrites a prior value, whether the policy takes effect immediately, or whether related rules are affected — material gaps for a destructive write.

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?

Front-loads the scope, then lists keys, then delivers the caveat — an efficient ordering with no filler. The rule enumeration is slightly redundant with the schema's rule description, costing a bit of tightness.

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

Completeness3/5

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

For a two-parameter destructive tool with no output schema, the description covers keys, value format, and one semantic trap. It omits whether the rule persists across sessions, how invalid rule names fail, and how this interacts with clear_policy_rule, leaving an agent to discover those at runtime.

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 the baseline is 3; the description earns an extra point by explaining what maxValue actually caps and why it is insufficient alone, which is meaning the schema's 'The value' text does not supply.

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 — 'Set one rule on the local signing policy' — and enumerates the exact rule keys accepted. This clearly separates it from siblings like get_policy and clear_policy_rule without needing their schemas.

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?

The phrase 'one rule' signals one-rule-per-call usage, and the closing sentence guides which rule to prefer for bounding token movement. It never explicitly names get_policy or clear_policy_rule as alternatives, so tool-selection guidance is implied rather than stated.

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