reset-api-key

THE RISK

Medium Risk

Why reset-api-key needs a policy

The tool resets an API key for a user, which is a modification action (Write) — it invalidates the old key and generates a new one. This is reversible in the sense that a new key is issued, but it does break existing authenticated sessions/integrations. The description is very brief ('Reset a user'), which reduces confidence.

From the tool's definition 'Reset a user' and tool name 'reset-api-key'

Documented attack patterns abuse exactly the kind of access reset-api-key gives an agent:

POLICY

How to control reset-api-key

PolicyLayer is an MCP gateway — it sits between your AI agents and Dynamic MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for reset-api-key:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "reset-api-key": {
      "limits": [
        {
          "counter": "reset-api-key_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

reset-api-key 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.

Create a free account and register Dynamic MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Dynamic MCP Server tools

Destructive delete-prompt Delete a prompt from the system Destructive delete-tool Delete a tool Destructive delete-user Delete a user Destructive remove-user Remove (delete) a user by email. This action is irreversible. You must confirm with the us Write add-prompt Add a new prompt to the system Write add-user Add a new user Write hide-tool Hide one or more tools for the current user Write share-tool Share a tool with another user (adds to their sharedTools array)

All 18 Dynamic MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about reset-api-key

What does the reset-api-key tool do? +

Reset a user. It is categorised as a Write tool in the Dynamic 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 reset-api-key? +

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

What risk level is reset-api-key? +

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

Can I rate-limit reset-api-key? +

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

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

reset-api-key is provided by the Dynamic MCP Server MCP server (scitara-cto/dynamic-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Dynamic MCP Server tool call.

Start from Dynamic MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →