AI agents use update_idea to create or update resources in UnClick — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
title | string | — | |
status | string | — | |
idea_id | string | Yes | |
agent_id | string | Yes | |
description | string | — |
Parameters from the server's own tool schema.
This tool creates or modifies data reversibly. An idea's title, description, and status can all be updated and subsequently reverted, which fits the Write category definition. While reversible, the medium severity reflects that an agent could spam, vandalize, or misrepresent ideas in a collaborative marketplace environment, affecting other users' experience and trust.
From the tool's definition Tool name 'update_idea' and description 'Edit an idea's title, description, or status' explicitly indicates modification of existing data. The allowed status values ('proposed', 'voting', 'locked', 'parked', 'rejected') show structured state changes.
Attacks that exploit this kind of access
Edit an idea's title, description, or status ('proposed', 'voting', 'locked', 'parked', 'rejected'). agent_id required. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update_idea accepts 5 parameters: title, status, idea_id, agent_id, description. Required: idea_id, agent_id. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for update_idea: 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 UnClick. Nothing to install.
update_idea 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 update_idea 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 update_idea. 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.
update_idea is provided by the UnClick MCP server (@unclick/mcp-server). 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 →