tool_with_context
AI agents call tool_with_context as a supporting operation in F5 MCP Server workflows.
With an empty description and a generic name that provides no semantic signal about the tool's function, it is impossible to reliably classify this tool. The server context suggests it could be anything from read to destructive, but without evidence the category defaults to Other with very low confidence.
From the tool's definition Tool name is 'tool_with_context' and description is empty — no actionable information available to determine what this tool does.
Attacks that exploit this kind of access
tool_with_context. It is categorised as a Other tool in the F5 MCP Server MCP Server, which means it performs auxiliary operations.
Register the F5 MCP Server MCP server in PolicyLayer and add a rule for tool_with_context: 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.
tool_with_context is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the tool_with_context 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 tool_with_context. 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.
tool_with_context 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 →