AI agents call getUsers to retrieve information from MCP Server Generator without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name suggests a query operation that retrieves user data without modification. With an empty description, confidence is reduced, but the semantic intent of 'getUsers' clearly points to a Read operation (retrieve/query) rather than write, execute, or destructive actions. Low severity assigned as it retrieves data without immediate blast radius unless user data is highly sensitive (unknown context).
From the tool's definition Tool name 'getUsers' indicates data retrieval with no side effects mentioned. Description is empty, limiting certainty.
Documented attack patterns abuse exactly the kind of access getUsers gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Server Generator, and nothing reaches the server without passing your rules. This is the rule we recommend for getUsers:
{
"version": "1",
"default": "deny",
"tools": {
"getUsers": {}
}
} getUsers is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
getUsers. It is categorised as a Read tool in the MCP Server Generator MCP Server, which means it retrieves data without modifying state.
Register the MCP Server Generator MCP server in PolicyLayer and add a rule for getUsers: 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 MCP Server Generator. Nothing to install.
getUsers 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 getUsers 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 getUsers. 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.
getUsers is provided by the MCP Server Generator MCP server (serhatuzbas/mcp-server-generator). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Server Generator, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
79 MCP Server Generator tools catalogued and risk-classified — across an index of 43,000+ MCP servers.