This record as markdown: /tools/281287994w-art-itick-mcp-server/single-depth.md
What single_depth does on Itick
AI agents call single_depth to retrieve information from Itick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why single_depth is rated Low
This tool retrieves market depth data (order book information) for a single security. Depth data is a read-only query of market state with no side effects, consistent with the server's stated purpose of exposing market data endpoints. The empty description lowers confidence slightly, but the naming pattern and server context strongly indicate a read operation.
From the tool's definition Tool name 'single_depth' and sibling tools (batch_depths, batch_klines, batch_quotes, batch_ticks) are all data retrieval patterns. Server description states it 'provides market data' including 'depth'.
Attacks that exploit this kind of access
The rule that runs single_depth safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Itick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For single_depth, this is the rule to start with:
single_depth 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 Itick, apply this rule, and every single_depth call is checked against it from then on.
Questions about single_depth
single_depth is a read tool on the Itick MCP server. It is categorised as a Read tool in the Itick MCP Server, which means it retrieves data without modifying state.
Register the Itick MCP server in PolicyLayer and add a rule for single_depth: 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 Itick. Nothing to install.
single_depth 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 single_depth 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 single_depth. 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.
single_depth is provided by the Itick MCP server (281287994w-art/itick-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Itick, and thousands of servers like it.
This server
Across the catalogue