为现有云代理添加后续指令。
AI agents use add_cursor_agent_followup_tool to create or update resources in ShowDoc MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ShowDoc MCP Server environment.
This tool creates or appends new instructions to an existing cloud agent configuration, which is a reversible modification of data. It does not execute arbitrary code, delete data, or move money. The 'cloud agent' context and instruction-modification capability suggest it could influence agent behavior, hence medium severity rather than low.
From the tool's definition Tool name contains 'add' and description translates to 'Add follow-up instructions to existing cloud agent.' The 'add' verb indicates creation/modification of data (new instructions attached to an agent).
Attacks that exploit this kind of access
为现有云代理添加后续指令。. It is categorised as a Write tool in the ShowDoc MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ShowDoc MCP Server MCP server in PolicyLayer and add a rule for add_cursor_agent_followup_tool: 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 ShowDoc MCP Server. Nothing to install.
add_cursor_agent_followup_tool 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 add_cursor_agent_followup_tool 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 add_cursor_agent_followup_tool. 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.
add_cursor_agent_followup_tool is provided by the ShowDoc MCP Server MCP server (yfcyfc123234/showdoc_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 →