tm_post_tool · F5 MCP Server MCP: Risk & Policy

WHAT IT DOES

What tm_post_tool does on F5 MCP Server

AI agents invoke tm_post_tool to trigger actions in F5 MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why tm_post_tool needs a policy

This tool issues HTTP POST requests to the F5 iControl REST API, which can both create new resources (Write) and trigger arbitrary actions/operations on F5 network infrastructure (Execute). Since it can execute actions—not just create data—and operates on critical network infrastructure (virtual servers, pools, iRules, etc.), the most severe applicable category is Execute.

From the tool's definition TMOS API POST. path에 리소스 생성 또는 액션 실행 ('resource creation or action execution')

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tm_post_tool Rate-limited

tm_post_tool stays usable, but rate-capped — a runaway agent can't fire it dozens of times 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_post_tool": {
      "limits": [
        {
          "counter": "tm_post_tool_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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_post_tool

What does the tm_post_tool tool do? +

TMOS API POST. path에 리소스 생성 또는 액션 실행. body는 API 스펙의 속성 (camelCase). It is categorised as a Execute tool in the F5 MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on tm_post_tool? +

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

tm_post_tool is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit tm_post_tool? +

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

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

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