AI agents use idea_submit to create or update resources in Tools — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tools environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
tags | array | — | Tags |
title | string | Yes | Idea title (max 200 chars) |
source | string | — | Source (user/v2ex/zhihu/reddit/agent, default: agent) |
category | string | — | Category (default: 工具需求) |
priority | string | — | Priority (default: medium) |
description | string | — | Detailed description (max 2000 chars) |
Parameters from the server's own tool schema.
This tool creates a new record (an idea/feature request) in a board system. The operation is reversible (ideas can typically be deleted or archived), does not execute external commands or code, does not delete or destroy data, and involves no financial transactions. It is a straightforward Write operation with low blast radius—the worst outcome of misuse would be spam or inappropriate submissions to an ideas board.
From the tool's definition Tool description states 'Submit a new idea or feature request' and 'Supports categorization, priority, and source tracking.' The verb 'submit' indicates creation of new data in a system.
Attacks that exploit this kind of access
Submit a new idea or feature request to the JieBang ideas board. Supports categorization, priority, and source tracking. It is categorised as a Write tool in the Tools MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
idea_submit accepts 6 parameters: tags, title, source, category, priority, description. Required: title. The full parameter table on this page comes from the server's own tool schema.
Register the Tools MCP server in PolicyLayer and add a rule for idea_submit: 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 Tools. Nothing to install.
idea_submit 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 idea_submit 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 idea_submit. 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.
idea_submit is provided by the Tools MCP server (https://www.jiebang.site/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 →