lsp_rename_tool

Propose a rename refactor (888_HOLD required).

SERVERArifos SOURCEarifos

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/io-github-ariffazil-aaa-mcp/lsp-rename-tool.md

WHAT IT DOES

What lsp_rename_tool does on Arifos

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

RISK

Why lsp_rename_tool is rated Medium

This tool creates or modifies refactor proposals in what appears to be a Language Server Protocol (LSP) context, making it a Write operation—it produces new artifacts or alters code metadata reversibly. It is not a Read (passive query), not Execute (no code execution triggered), not Destructive (changes are refactoring proposals, not deletions), and not Financial.

From the tool's definition Tool is called 'lsp_rename_tool' and described as 'Propose a rename refactor'. A rename refactor modifies code identifiers, which is a reversible code change operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs lsp_rename_tool safely

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

lsp_rename_tool Rate-limited

lsp_rename_tool 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": {
    "lsp_rename_tool": {
      "limits": [
        {
          "counter": "lsp_rename_tool_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 Arifos, apply this rule, and every lsp_rename_tool call is checked against it from then on.

FAQ

Questions about lsp_rename_tool

What does the lsp_rename_tool tool do? +

Propose a rename refactor (888_HOLD required). It is categorised as a Write tool in the Arifos MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on lsp_rename_tool? +

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

What risk level is lsp_rename_tool? +

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

Can I rate-limit lsp_rename_tool? +

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

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

lsp_rename_tool is provided by the Arifos MCP server (arifos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Arifos, and thousands of servers like it.

This server

All 91 Arifos tools →

Across the catalogue

The MCP Attack Database →

Guides

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