limpar_selecao

Limpa a seleção atual do editor. Inserções subsequentes irão para a raiz da página.

SERVERAtomik Dev SOURCE@atomik-dev/mcp

Low RISK CLASS

Category Other

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/atomik-dev-mcp/limpar-selecao.md

WHAT IT DOES

What limpar_selecao does on Atomik Dev

AI agents call limpar_selecao as a supporting operation in Atomik Dev workflows.

RISK

Why limpar_selecao is rated Low

Without any rule in front of it, every call an agent makes to limpar_selecao happens silently: no trail, no cap, no way to know it misbehaved until something breaks downstream.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs limpar_selecao safely

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

limpar_selecao Rate-limited

limpar_selecao gets a rate cap, and everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "limpar_selecao": {
      "limits": [
        {
          "counter": "limpar_selecao_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

SET A RULE FOR THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Atomik Dev, apply this rule, and every limpar_selecao call is checked against it from then on.

FAQ

Questions about limpar_selecao

What does the limpar_selecao tool do? +

Limpa a seleção atual do editor. Inserções subsequentes irão para a raiz da página. It is categorised as a Other tool in the Atomik Dev MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on limpar_selecao? +

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

What risk level is limpar_selecao? +

limpar_selecao is a Other tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit limpar_selecao? +

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

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

limpar_selecao is provided by the Atomik Dev MCP server (@atomik-dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Atomik Dev, and thousands of servers like it.

This server

All 64 Atomik Dev tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Tool risk categories →MCP tool →