create_proposal
AI agents use create_proposal to create or update resources in Clink MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Clink MCP Server environment.
The tool creates a proposal object within a collaboration/coordination system. This is a Write action because it creates new data that can be modified or deleted by users. Severity is medium because proposals in a group coordination system could influence team decisions, but the effect depends on how proposals are used and whether they bind actions.
From the tool's definition Tool name 'create_proposal' suggests data creation. Server context shows it enables group messaging, project tracking, and milestone management with tools like 'create_project' and 'create_milestone' that create reversible data structures.
Attacks that exploit this kind of access
create_proposal. It is categorised as a Write tool in the Clink MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Clink MCP Server MCP server in PolicyLayer and add a rule for create_proposal: 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 Clink MCP Server. Nothing to install.
create_proposal 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 create_proposal 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 create_proposal. 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.
create_proposal is provided by the Clink MCP Server MCP server (voxos-ai-inc/clink-mcp-server-python). 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 →