Discover Tasks \u00b7 query discoverTask. Variables: after, filter, first, order, after1, filter1, first1, order1, after2, filter2, first2, order2, after3, filter3, first3, order3, after4, filter4, first4, order4, after5, first5, after6, first6, after7, first7, after8, first8, after9, filter5, fi...
AI agents call discover_task to retrieve information from ReliaQuest GreyMatter MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a query tool for discovering/listing tasks within the GreyMatter platform. The presence of pagination (after, first) and filtering parameters confirms it retrieves data without modifying or deleting anything. No side effects or state changes are indicated. Read operations on incident response task data pose minimal risk unless the data itself is highly sensitive, but the tool itself performs no risky actions.
From the tool's definition Tool name 'discover_task' and description 'Discover Tasks · query discoverTask' indicates a read-only query operation.
Attacks that exploit this kind of access
Discover Tasks \u00b7 query discoverTask. Variables: after, filter, first, order, after1, filter1, first1, order1, after2, filter2, first2, order2, after3, filter3, first3, order3, after4, filter4, first4, order4, after5, first5, after6, first6, after7, first7, after8, first8, after9, filter5, first9, order5, after10, first10, after11, first11, by. Example variables: {\. It is categorised as a Read tool in the ReliaQuest GreyMatter MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ReliaQuest GreyMatter MCP Server MCP server in PolicyLayer and add a rule for discover_task: 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 ReliaQuest GreyMatter MCP Server. Nothing to install.
discover_task 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 discover_task 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 discover_task. 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.
discover_task is provided by the ReliaQuest GreyMatter MCP Server MCP server (space-c0wboy/reliaquest-greymatter-mcp-server). 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 →