This record as markdown: /tools/funny-booth-aos-mcp-server/get-tasks.md
What get_tasks does on Aos
AI agents call get_tasks to retrieve information from Aos without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
date | string | — | 対象日 YYYY-MM-DD |
status | string | — | ステータス絞り込み |
team_id | string | — | 対象チームID（省略時はユーザーの既定チーム） |
Parameters from the server's own tool schema.
Why get_tasks is rated Low
The tool retrieves or queries task data with no mutations or external side effects. Even without an explicit description, the naming convention and server context strongly suggest a read-only retrieval function. Confidence is slightly reduced due to the empty description, but the name and context provide sufficient evidence for Read classification with low severity.
From the tool's definition Tool name 'get_tasks' indicates a retrieval operation with no side effects. The verb 'get' is characteristic of query/fetch operations. Description is empty, limiting full context, but sibling tools on the server (create_task, create_issue, complete_task, etc.
Attacks that exploit this kind of access
The rule that runs get_tasks 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 get_tasks, this is the rule to start with:
get_tasks is read-only, so it stays allowed. 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 get_tasks call is checked against it from then on.
Questions about get_tasks
get_tasks is a read tool on the Aos MCP server. It is categorised as a Read tool in the Aos MCP Server, which means it retrieves data without modifying state.
get_tasks accepts 3 parameters: date, status, team_id. 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 get_tasks: 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.
get_tasks is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_tasks 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 get_tasks. 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.
get_tasks 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