Manage pipeline stages and deals. Actions: create_stage, list_stages, create_deal, update_deal, list_deals.
AI agents use manage_pipeline 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.
The tool primarily creates and updates pipeline stages and deals, which are reversible write operations on business data. While the tool includes list_stages and list_deals (Read operations), the presence of create and update operations makes the overall tool a Write-category risk.
From the tool's definition The tool performs create_stage, create_deal, update_deal, and list_deals operations. Creating and updating deals constitutes modification of business-critical data structures.
Attacks that exploit this kind of access
Manage pipeline stages and deals. Actions: create_stage, list_stages, create_deal, update_deal, list_deals. 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_pipeline: 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_pipeline 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_pipeline 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_pipeline. 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_pipeline 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 →