tm_put_tool · F5 MCP Server MCP: Risk & Policy

WHAT IT DOES

What tm_put_tool does on F5 MCP Server

AI agents use tm_put_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_put_tool needs a policy

PUT is a write operation that modifies/replaces entire resource configurations. While not destructive in the strict sense (replacement can theoretically be reversed), it has significant blast radius if an AI agent misconfigures critical F5 load balancing or security objects. Classified as Write rather than Execute because it is primarily data modification, not arbitrary code/command execution.

From the tool's definition Tool description states 'TMOS API PUT' with 'body는 전체 속성 (교체)' (body contains full properties for replacement). PUT operations modify/replace entire resources.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tm_put_tool Rate-limited

tm_put_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_put_tool": {
      "limits": [
        {
          "counter": "tm_put_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_put_tool

What does the tm_put_tool tool do? +

TMOS API PUT. path는 리소스까지 포함. 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_put_tool? +

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

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

Can I rate-limit tm_put_tool? +

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

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

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