delete_stacks_api_url

Remove the custom Stacks API URL and revert to the default Hiro API (api.mainnet.hiro.so or api.testnet.hiro.so).

SERVERAibtc SOURCEaibtcdev/aibtc-mcp-server

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/io-github-aibtcdev-mcp-server/delete-stacks-api-url.md

WHAT IT DOES

What delete_stacks_api_url does on Aibtc

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

RISK

Why delete_stacks_api_url is rated Medium

This tool deletes a configuration setting (custom API URL) and reverts to a default value. While it's described as 'remove', it's a reversible configuration change — the custom URL can be re-set. It modifies system configuration rather than irreversibly destroying data, so Write is more appropriate than Destructive.

From the tool's definition Remove the custom Stacks API URL and revert to the default Hiro API

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_stacks_api_url safely

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

delete_stacks_api_url Rate-limited

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

FAQ

Questions about delete_stacks_api_url

What does the delete_stacks_api_url tool do? +

Remove the custom Stacks API URL and revert to the default Hiro API (api.mainnet.hiro.so or api.testnet.hiro.so). It is categorised as a Write tool in the Aibtc MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on delete_stacks_api_url? +

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

What risk level is delete_stacks_api_url? +

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

Can I rate-limit delete_stacks_api_url? +

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

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

delete_stacks_api_url is provided by the Aibtc MCP server (aibtcdev/aibtc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Aibtc, and thousands of servers like it.

This server

All 358 Aibtc tools →

Across the catalogue

The MCP Attack Database →

Guides

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