Search for opportunities with optional filters
AI agents call autotask_search_opportunities to retrieve information from Autotask MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves opportunity records based on filter criteria. It has no side effects, does not create, modify, or delete data, and does not execute external operations or move money. It is a straightforward read operation typical of PSA systems for lookup and discovery tasks.
From the tool's definition Tool name contains 'search' and description states 'Search for opportunities with optional filters' — a query operation with no modification or deletion of data.
Attacks that exploit this kind of access
Search for opportunities with optional filters. It is categorised as a Read tool in the Autotask MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Autotask MCP Server MCP server in PolicyLayer and add a rule for autotask_search_opportunities: 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 MCP Server. Nothing to install.
autotask_search_opportunities 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_opportunities 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_opportunities. 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_opportunities is provided by the Autotask MCP Server MCP server (ticnine/autotask-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 →