This record as markdown: /tools/funny-booth-aos-mcp-server/create-issue.md
What create_issue does on Aos
AI agents use create_issue to create or update resources in Aos, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Aos environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
title | string | Yes | イシュー名 |
status | string | — | |
team_id | string | — | 対象チームID（省略時はユーザーの既定チーム） |
priority | number | — | |
description | string | — |
Parameters from the server's own tool schema.
Why create_issue is rated Medium
The tool name suggests creating an issue record in a project management system. Without a description, I infer from context that this likely creates a new issue entity reversibly. This is a Write operation (creates/modifies data without deletion or side effects).
From the tool's definition Tool named 'create_issue' with no description. Sibling tools include create_task, create_todo, create_backlog_item, and delete_backlog_item, suggesting a project/task management system. 'Create' operations are Write category.
Attacks that exploit this kind of access
The rule that runs create_issue safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_issue, this is the rule to start with:
create_issue stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Aos, apply this rule, and every create_issue call is checked against it from then on.
Questions about create_issue
create_issue is a write tool on the Aos MCP server. It is categorised as a Write tool in the Aos MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_issue accepts 5 parameters: title, status, team_id, priority, description. Required: title. The full parameter table on this page comes from the server's own tool schema.
Register the Aos MCP server in PolicyLayer and add a rule for create_issue: 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 Aos. Nothing to install.
create_issue 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_issue 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_issue. 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_issue is provided by the Aos MCP server (@funny-booth/aos-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aos, and thousands of servers like it.
This server
Across the catalogue