AI agents call board_my_tasks to retrieve information from Agent Board without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns task data without modifying, deleting, or executing any operations. It is a straightforward data retrieval function that falls squarely within the Read category. Severity is low because unauthorized access to one agent's task list has limited blast radius in a multi-agent orchestration system.
From the tool's definition Tool name 'board_my_tasks' and description 'List tasks assigned to a specific agent' indicate a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access board_my_tasks gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Agent Board, and nothing reaches the server without passing your rules. This is the rule we recommend for board_my_tasks:
{
"version": "1",
"default": "deny",
"tools": {
"board_my_tasks": {}
}
}board_my_tasks is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List tasks assigned to a specific agent. It is categorised as a Read tool in the Agent Board MCP Server, which means it retrieves data without modifying state.
Register the Agent Board MCP server in PolicyLayer and add a rule for board_my_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 Agent Board. Nothing to install.
board_my_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 board_my_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 board_my_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.
board_my_tasks is provided by the Agent Board MCP server (quentintou/agent-board). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Agent Board, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
14 Agent Board tools catalogued and risk-classified — across an index of 43,000+ MCP servers.