tm_patch_tool · F5 MCP Server MCP: Risk & Policy

WHAT IT DOES

What tm_patch_tool does on F5 MCP Server

AI agents use tm_patch_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 tm_patch_tool needs a policy

This tool issues HTTP PATCH requests to modify existing F5 resources (pools, virtual servers, profiles, etc.) in a reversible manner. PATCH updates properties without deletion, making it a Write operation.

From the tool's definition Tool name contains 'patch' and description explicitly states 'TMOS API PATCH' with 'body는 변경할 속성만' (body contains only properties to change), indicating it modifies existing F5 configuration objects.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tm_patch_tool Rate-limited

tm_patch_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": {
    "tm_patch_tool": {
      "limits": [
        {
          "counter": "tm_patch_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 tm_patch_tool

What does the tm_patch_tool tool do? +

TMOS API PATCH. path는 리소스까지 포함 (예: ltm/pool/~Common~my_pool). body는 변경할 속성만. 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 tm_patch_tool? +

Register the F5 MCP Server MCP server in PolicyLayer and add a rule for tm_patch_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 tm_patch_tool? +

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

Can I rate-limit tm_patch_tool? +

Yes. Add a rate_limit block to the tm_patch_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 tm_patch_tool completely? +

Set action: deny in the PolicyLayer policy for tm_patch_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 tm_patch_tool? +

tm_patch_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.