List all users in your Kinsta company.
AI agents call kinsta.company.users to retrieve information from Kinsta MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries user data from the Kinsta company account without creating, modifying, or deleting anything. It is a pure information retrieval operation. Severity is low because user listing is generally low-risk unless the company has extremely sensitive user data, but exposure is still limited in scope compared to infrastructure or financial operations.
From the tool's definition Tool name includes 'list' semantics and description explicitly states 'List all users' — a read-only query operation with no side effects.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
List all users in your Kinsta company. It is categorised as a Read tool in the Kinsta MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Kinsta MCP Server MCP server in PolicyLayer and add a rule for kinsta.company.users: 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 Kinsta MCP Server. Nothing to install.
kinsta.company.users 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 kinsta.company.users 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 kinsta.company.users. 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.
kinsta.company.users is provided by the Kinsta MCP Server MCP server (jacob-hartmann/kinsta-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 →