generate_password · Nexus Core MCP: Risk & Policy

WHAT IT DOES

What generate_password does on Nexus Core

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

WHY IT NEEDS A POLICY

Why generate_password needs a policy

An AI agent can call generate_password faster than any human can review — one bad instruction and it creates or modifies resources in Nexus Core by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_password Rate-limited

generate_password 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": {
    "generate_password": {
      "limits": [
        {
          "counter": "generate_password_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 Nexus Core, so you can run agents against it safely.

FAQ

Questions about generate_password

What does the generate_password tool do? +

Generate one or more cryptographically random passwords. It is categorised as a Write tool in the Nexus Core MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on generate_password? +

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

What risk level is generate_password? +

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

Can I rate-limit generate_password? +

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

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

generate_password is provided by the Nexus Core MCP server (noumenon-ai/nexus-core). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.