TMOS API GET. path는 tm 하위 경로 (예: ltm/pool, ltm/pool/~Common~my_pool, net/vlan, sys/syslog).
AI agents call tm_get_tool to retrieve information from F5 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that queries F5 configuration objects and returns their state. It has no side effects, cannot modify data, and poses minimal risk even if misused by an AI agent—the worst outcome would be unauthorized information disclosure about network infrastructure configuration, which is lower severity than write/execute/destructive operations.
From the tool's definition Tool name contains 'get' and description explicitly states 'TMOS API GET'. The function retrieves configuration data from F5 devices via iControl REST API without modifying state.
Attacks that exploit this kind of access
TMOS API GET. path는 tm 하위 경로 (예: ltm/pool, ltm/pool/~Common~my_pool, net/vlan, sys/syslog). It is categorised as a Read tool in the F5 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the F5 MCP Server MCP server in PolicyLayer and add a rule for tm_get_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.
tm_get_tool is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the tm_get_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.
Set action: deny in the PolicyLayer policy for tm_get_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.
tm_get_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →