Search for notes on a specific project. Fan-out across many projects trips Autotask\
AI agents call autotask_search_project_notes to retrieve information from Autotask 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 project notes without creating, modifying, or deleting data. It is a read-only operation with no side effects. The warning about 'fan-out across many projects' is a performance/rate-limiting concern, not a security risk that would elevate the category.
From the tool's definition Tool name contains 'search' and description states 'Search for notes on a specific project' — retrieves data without modification.
Documented attack patterns abuse exactly the kind of access autotask_search_project_notes gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Autotask, and nothing reaches the server without passing your rules. This is the rule we recommend for autotask_search_project_notes:
{
"version": "1",
"default": "deny",
"tools": {
"autotask_search_project_notes": {}
}
} autotask_search_project_notes 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.
Search for notes on a specific project. Fan-out across many projects trips Autotask\. It is categorised as a Read tool in the Autotask MCP Server, which means it retrieves data without modifying state.
Register the Autotask MCP server in PolicyLayer and add a rule for autotask_search_project_notes: 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 Autotask. Nothing to install.
autotask_search_project_notes 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 autotask_search_project_notes 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 autotask_search_project_notes. 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.
autotask_search_project_notes is provided by the Autotask MCP server (wyre-technology/autotask-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Autotask, 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.
91 Autotask tools catalogued and risk-classified — across an index of 43,000+ MCP servers.