tab_close

Close the current chart tab

SERVERTradingView MCP Bridge SOURCEbyeung888/tradingview-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/byeung888-tradingview-mcp/tab-close.md

WHAT IT DOES

What tab_close does on TradingView MCP Bridge

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

RISK

Why tab_close is rated Medium

An AI agent can call tab_close faster than any human can review: one bad instruction and it creates or modifies resources in TradingView MCP Bridge by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs tab_close safely

PolicyLayer is an MCP gateway: it sits between your AI agents and TradingView MCP Bridge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For tab_close, this is the rule to start with:

tab_close Rate-limited

tab_close 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": {
    "tab_close": {
      "limits": [
        {
          "counter": "tab_close_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect TradingView MCP Bridge, apply this rule, and every tab_close call is checked against it from then on.

FAQ

Questions about tab_close

What does the tab_close tool do? +

Close the current chart tab. It is categorised as a Write tool in the TradingView MCP Bridge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on tab_close? +

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

What risk level is tab_close? +

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

Can I rate-limit tab_close? +

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

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

tab_close is provided by the TradingView MCP Bridge MCP server (byeung888/tradingview-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on TradingView MCP Bridge, and thousands of servers like it.

This server

All 78 TradingView MCP Bridge tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →