market_query
A read tool on the Container- MCP server.
This record as markdown: /tools/54rt1n-container-mcp/market-query.md
What market_query does on Container-MCP
AI agents call market_query to retrieve information from Container-MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why market_query is rated Low
The tool name contains 'query', which typically indicates retrieval without side effects. No description is provided, so confidence is reduced accordingly. Without evidence of modification, deletion, or financial operations, Read is the most probable classification.
From the tool's definition Tool name 'market_query' suggests data retrieval/querying based on the 'query' verb, consistent with Read operations like 'search, list, get, fetch'. Description is empty, limiting certainty.
Attacks that exploit this kind of access
The rule that runs market_query safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Container-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For market_query, this is the rule to start with:
market_query is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Container-MCP, apply this rule, and every market_query call is checked against it from then on.
Questions about market_query
market_query is a read tool on the Container MCP server. It is categorised as a Read tool in the Container-MCP MCP Server, which means it retrieves data without modifying state.
Register the Container MCP server in PolicyLayer and add a rule for market_query: 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 Container-MCP. Nothing to install.
market_query 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 market_query 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 market_query. 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.
market_query is provided by the Container MCP server (54rt1n/container-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Container, and thousands of servers like it.
This server
Across the catalogue