close_connection · UOFast MCP: Risk & Policy

WHAT IT DOES

What close_connection does on UOFastMCP

AI agents use close_connection to create or update resources in UOFastMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UOFastMCP environment.

WHY IT NEEDS A POLICY

Why close_connection needs a policy

This tool modifies the internal connection state by removing an entry from the cache. While it affects system state, it is reversible and has no destructive impact on actual database data or records. It does not create external side effects like Execute tools do, nor is it irreversible like Destructive tools. It is Write-category because it alters cached connection metadata.

From the tool's definition Tool 'close_connection' removes a specific connection from the cache, which is a reversible state change (the connection can be re-added via add_connection). The description indicates a cleanup/cache management operation rather than data deletion.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

close_connection Rate-limited

close_connection 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": {
    "close_connection": {
      "limits": [
        {
          "counter": "close_connection_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 UOFastMCP, so you can run agents against it safely.

FAQ

Questions about close_connection

What does the close_connection tool do? +

Close and remove a specific connection from the cache. It is categorised as a Write tool in the UOFastMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on close_connection? +

Register the UOFast MCP server in PolicyLayer and add a rule for close_connection: 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 UOFastMCP. Nothing to install.

What risk level is close_connection? +

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

Can I rate-limit close_connection? +

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

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

close_connection is provided by the UOFast MCP server (rokipark/uofastmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.