add_to_trust_tool · F5 MCP Server MCP: Risk & Policy

WHAT IT DOES

What add_to_trust_tool does on F5 MCP Server

AI agents use add_to_trust_tool to create or update resources in F5 MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your F5 MCP Server environment.

WHY IT NEEDS A POLICY

Why add_to_trust_tool needs a policy

This tool creates or modifies configuration (adding a peer to a trust domain) rather than deleting it, placing it in Write category. Severity is high because adding devices to trust domains affects network security boundaries and HA/cluster operations—misconfiguration could lead to unauthorized device pairing or security exposure.

From the tool's definition Tool adds a peer device to a trust domain on the connected F5 device. The operation modifies F5 configuration by establishing trust relationships between devices, which is reversible but impacts device cluster security and connectivity.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_to_trust_tool Rate-limited

add_to_trust_tool stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_to_trust_tool": {
      "limits": [
        {
          "counter": "add_to_trust_tool_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches F5 MCP Server, so you can run agents against it safely.

FAQ

Questions about add_to_trust_tool

What does the add_to_trust_tool tool do? +

현재 연결된 장비(Primary)에서 피어 장비를 trust 도메인에 추가. REST API를 먼저 시도하고 403일 때만 TMSH 폴백. 반환: ok, method(REST|TMSH_fallback), response 등. It is categorised as a Write tool in the F5 MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_to_trust_tool? +

Register the F5 MCP Server MCP server in PolicyLayer and add a rule for add_to_trust_tool: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches F5 MCP Server. Nothing to install.

What risk level is add_to_trust_tool? +

add_to_trust_tool is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_to_trust_tool? +

Yes. Add a rate_limit block to the add_to_trust_tool rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block add_to_trust_tool completely? +

Set action: deny in the PolicyLayer policy for add_to_trust_tool. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides add_to_trust_tool? +

add_to_trust_tool is provided by the F5 MCP Server MCP server (mink0119/f5-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.