Get all action items from the local database. Automatically performs incremental sync first to ensure data is fresh. Can filter by assignee, completion status, or date range.
AI agents call get_all_action_items to retrieve information from Fellow MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves action items from a local SQLite cache with optional filtering. It performs an automatic sync to refresh data but does not create, modify, delete, or execute any operations—it only reads and filters existing data.
From the tool's definition Tool retrieves data ('Get all action items from the local database') with filtering capabilities (by assignee, completion status, or date range).
Attacks that exploit this kind of access
Get all action items from the local database. Automatically performs incremental sync first to ensure data is fresh. Can filter by assignee, completion status, or date range. It is categorised as a Read tool in the Fellow MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Fellow MCP Server MCP server in PolicyLayer and add a rule for get_all_action_items: 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 Fellow MCP Server. Nothing to install.
get_all_action_items 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_all_action_items 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_all_action_items. 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_all_action_items is provided by the Fellow MCP Server MCP server (liba2k/unofficial-fellow-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 →