query_data
AI agents call query_data to retrieve information from Massive Com MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite the empty description, the name 'query_data' combined with the server's purpose (providing LLM-friendly interface to financial data) indicates a read operation that retrieves data. Severity is medium due to potential sensitivity of financial data that could be exposed if queried without proper safeguards.
From the tool's definition Tool name 'query_data' and server context indicates data retrieval from financial API. Description is empty, which reduces confidence. Sibling tools 'call_api' and 'search_endpoints' suggest this queries stored financial data rather than modifying it.
Attacks that exploit this kind of access
query_data. It is categorised as a Read tool in the Massive Com MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Massive Com MCP Server MCP server in PolicyLayer and add a rule for query_data: 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 Massive Com MCP Server. Nothing to install.
query_data 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 query_data 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 query_data. 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.
query_data is provided by the Massive Com MCP Server MCP server (massive-com/mcp_massive). 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 →