Medium Risk

tl_close_tab

Close a browser tab by role or URL pattern.

Part of the Tronlink server.

tl_close_tab can modify Tronlink data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE TRONLINK →

Free to start. No card required.

AI agents use tl_close_tab to create or modify resources in Tronlink. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call tl_close_tab repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Tronlink.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "tl_close_tab": {
      "limits": [
        {
          "counter": "tl_close_tab_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Tronlink policy for all 55 tools.

Get this rule live on your own Tronlink server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY TRONLINK →

View all 55 tools →

These attack patterns abuse exactly the kind of access tl_close_tab gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so tl_close_tab only ever does what you allow.

SECURE TRONLINK →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the tl_close_tab tool do? +

Close a browser tab by role or URL pattern.. It is categorised as a Write tool in the Tronlink MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on tl_close_tab? +

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

What risk level is tl_close_tab? +

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

Can I rate-limit tl_close_tab? +

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

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

tl_close_tab is provided by the Tronlink MCP server (@tronlink/mcp-server-tronlink). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Tronlink tool call.

Deterministic rules across all 55 Tronlink tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.