List redirect rules for an environment. Supports filtering and pagination.
AI agents call kinsta.environments.redirects 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 queries and returns existing redirect rule data without creating, modifying, deleting, or executing any changes. It has no side effects and poses minimal risk even if an AI agent misuses it—at worst, it reveals configuration information already stored in the system.
From the tool's definition Tool description states 'List redirect rules for an environment. Supports filtering and pagination.' The verb 'List' and absence of any modification, deletion, or execution language indicates a retrieval-only operation.
Attacks that exploit this kind of access
List redirect rules for an environment. Supports 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.environments.redirects: 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.environments.redirects 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.environments.redirects 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.environments.redirects. 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.environments.redirects 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 →