AI agents use update_qiita_article to create or update resources in Qiita — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Qiita environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
body | string | Yes | Markdown formatted content |
tags | array | — | List of tags for the article |
slide | boolean | — | Whether to enable slide mode |
title | string | Yes | Article title |
item_id | string | Yes | The ID of the article to update |
private | boolean | — | Whether the article is private |
organization_url_name | string | — | The url_name of the organization for the article |
Parameters from the server's own tool schema.
This tool modifies (updates) an article on Qiita, which is a reversible write operation. It does not delete or destroy data (would be Destructive), nor does it move money (Financial) or execute arbitrary code (Execute).
From the tool's definition Tool name 'update_qiita_article' and description 'update an existing Qiita article' clearly indicate modification of existing data.
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
update an existing Qiita article. It is categorised as a Write tool in the Qiita MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update_qiita_article accepts 7 parameters: body, tags, slide, title, item_id, private, organization_url_name. Required: body, title, item_id. The full parameter table on this page comes from the server's own tool schema.
Register the Qiita MCP server in PolicyLayer and add a rule for update_qiita_article: 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 Qiita. Nothing to install.
update_qiita_article 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_qiita_article 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_qiita_article. 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_qiita_article is provided by the Qiita MCP server (@2bo/qiita-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 →