manage_credentials · Asterdex MCP: Risk & Policy

WHAT IT DOES

What manage_credentials does on Asterdex

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

WHY IT NEEDS A POLICY

Why manage_credentials needs a policy

This tool modifies system configuration (API credentials) rather than deleting it irreversibly, placing it in Write rather than Destructive. However, it warrants 'high' severity because an AI agent with this capability could be tricked into setting attacker-controlled credentials, giving adversaries persistent access to the trading account.

From the tool's definition Tool name 'manage_credentials' with description 'Set or clear API credentials' indicates modification of authentication state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

manage_credentials Rate-limited

manage_credentials 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": {
    "manage_credentials": {
      "limits": [
        {
          "counter": "manage_credentials_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 Asterdex, so you can run agents against it safely.

FAQ

Questions about manage_credentials

What does the manage_credentials tool do? +

Set or clear API credentials. It is categorised as a Write tool in the Asterdex MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on manage_credentials? +

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

What risk level is manage_credentials? +

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

Can I rate-limit manage_credentials? +

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

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

manage_credentials is provided by the Asterdex MCP server (tyranosurasmax/asterdex-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.