add_dev_share · Basis MCP Server MCP: Risk & Policy

WHAT IT DOES

What add_dev_share does on Basis MCP Server

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

WHY IT NEEDS A POLICY

Why add_dev_share needs a policy

This tool creates or modifies token fee parameters by assigning dev fee share to a wallet. It is reversible (fees can be adjusted or removed later) and does not irreversibly delete data or move funds directly, so it is Write rather than Destructive or Financial. However, it could indirectly affect financial flows if misconfigured (e.g., sending fees to an attacker's wallet), warranting medium severity.

From the tool's definition Tool description states 'Add dev fee share to a wallet for your token' — this is a modification operation that updates fee distribution configuration for a token contract.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_dev_share Rate-limited

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

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Basis MCP Server, so you can run agents against it safely.

FAQ

Questions about add_dev_share

What does the add_dev_share tool do? +

Add dev fee share to a wallet for your token. It is categorised as a Write tool in the Basis MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_dev_share? +

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

What risk level is add_dev_share? +

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

Can I rate-limit add_dev_share? +

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

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

add_dev_share is provided by the Basis MCP Server MCP server (launch-on-basis/mcp-ts). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.