Generate random modern names.
AI agents call generate_name to retrieve information from RPG MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool generates random name data with no side effects, no data modification, no external operations, and no financial implications. It is a pure read/generation operation returning synthetic data, consistent with the RPG server's purpose of providing random content for gameplay.
From the tool's definition Generate random modern names
Attacks that exploit this kind of access
Generate random modern names. It is categorised as a Read tool in the RPG MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RPG MCP Server MCP server in PolicyLayer and add a rule for generate_name: 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 RPG MCP Server. Nothing to install.
generate_name is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the generate_name 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 generate_name. 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.
generate_name is provided by the RPG MCP Server MCP server (jnaskali/rpg-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 →