Generate multiple credentials of different types in a single operation for efficient bulk generation.
AI agents use generateBatch to create or update resources in My Credentials MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your My Credentials MCP Server environment.
The tool creates new credentials in bulk, which is a write operation that modifies the credential store by adding new records. While not destructive (data is not deleted or irreversibly overwritten), it does persistently create data.
From the tool's definition Tool name is 'generateBatch' and description states 'Generate multiple credentials of different types in a single operation for efficient bulk generation.' This creates/generates new credential records.
Attacks that exploit this kind of access
Generate multiple credentials of different types in a single operation for efficient bulk generation. It is categorised as a Write tool in the My Credentials MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the My Credentials MCP Server MCP server in PolicyLayer and add a rule for generateBatch: 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 My Credentials MCP Server. Nothing to install.
generateBatch is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the generateBatch 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.
Set action: deny in the PolicyLayer policy for generateBatch. 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.
generateBatch is provided by the My Credentials MCP Server MCP server (preangelleo/my-credentials-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →