Indicators \u00b7 query indicators. Variables: after, filter, first, order. Example variables: {\
AI agents call indicators 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.
The tool queries indicators without modifying, deleting, or executing operations. The parameters (after, filter, first, order) are typical pagination and filtering arguments for retrieving data sets. This is a read-only operation with no side effects or ability to modify underlying data.
From the tool's definition Tool name 'indicators' with description 'query indicators' and parameters 'after, filter, first, order' are consistent with a paginated data retrieval operation.
Attacks that exploit this kind of access
Indicators \u00b7 query indicators. Variables: after, filter, first, order. 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 indicators: 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.
indicators 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 indicators 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 indicators. 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.
indicators 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 →