AI agents call query_on_demand_data to retrieve information from Macrocosmos MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name and server description indicate this retrieves data from social media platforms in real-time without modifying it. Despite the empty description lowering confidence, the 'query' verb and data collection context point to Read category.
From the tool's definition Tool name 'query_on_demand_data' and server context describe querying from X (Twitter) and Reddit. The sibling tools (build_dataset, get_dataset_status) reinforce a data retrieval workflow. Tool description is empty, reducing confidence.
Documented attack patterns abuse exactly the kind of access query_on_demand_data gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Macrocosmos MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for query_on_demand_data:
{
"version": "1",
"default": "deny",
"tools": {
"query_on_demand_data": {}
}
}query_on_demand_data 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.
query_on_demand_data. It is categorised as a Read tool in the Macrocosmos MCP MCP Server, which means it retrieves data without modifying state.
Register the Macrocosmos MCP server in PolicyLayer and add a rule for query_on_demand_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 Macrocosmos MCP. Nothing to install.
query_on_demand_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_on_demand_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_on_demand_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_on_demand_data is provided by the Macrocosmos MCP server (macrocosm-os/macrocosmos-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Macrocosmos MCP, 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.
6 Macrocosmos MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.