Add, list, or delete redirect rules. Supports 301 (permanent) and 302 (temporary) redirects.
AI agents use manage_redirects to create or update resources in Inkwell MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Inkwell MCP Server environment.
This tool primarily enables creation and modification of redirect rules, which are configuration settings that can be changed or recreated. Although it includes a delete function, redirects are not permanent business data or content — they are easily restored or reconfigured. The tool falls into Write category as it modifies site behavior reversibly.
From the tool's definition Tool description states 'Add, list, or delete redirect rules' — the add and delete operations modify site configuration.
Attacks that exploit this kind of access
Add, list, or delete redirect rules. Supports 301 (permanent) and 302 (temporary) redirects. It is categorised as a Write tool in the Inkwell MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Inkwell MCP Server MCP server in PolicyLayer and add a rule for manage_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 Inkwell MCP Server. Nothing to install.
manage_redirects is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the manage_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 manage_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.
manage_redirects is provided by the Inkwell MCP Server MCP server (mumega-com/inkwell). 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 →