List all WordPress plugins across all sites in your Kinsta company. Supports search, filtering, and pagination.
AI agents call kinsta.company.plugins 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.
The tool retrieves and queries plugin data from Kinsta company sites without creating, modifying, deleting, or executing any actions on those plugins. It is a pure read operation with no side effects. The low severity reflects that listing installed plugins poses minimal risk—this information may be useful for reconnaissance but does not directly impact systems or data.
From the tool's definition Tool performs 'List all WordPress plugins across all sites' and 'Supports search, filtering, and pagination' — these are query and retrieval operations with no modification or execution of plugins.
Attacks that exploit this kind of access
List all WordPress plugins across all sites in your Kinsta company. Supports search, filtering, and pagination. 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.plugins: 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.plugins 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.plugins 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.plugins. 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.plugins 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 →