Low Risk

tiger_get_market_status

tiger_get_market_status

How to control tiger_get_market_status ↓

What tiger_get_market_status does on Tiger MCP

AI agents call tiger_get_market_status to retrieve information from Tiger MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why tiger_get_market_status needs a policy

This tool appears to fetch market status data (e.g., whether markets are open/closed, trading hours) without modifying any state, executing trades, or creating financial obligations. It fits the Read category as a data retrieval operation. Confidence is moderate (0.85) due to the empty description, but the naming convention and sibling tools context support this classification.

From the tool's definition Tool name 'tiger_get_market_status' indicates retrieval of market status information. No description provided, but the 'get_' prefix and context within a market analysis/trading server strongly suggests read-only data retrieval.

Documented attack patterns abuse exactly the kind of access tiger_get_market_status gives an agent:

How to control tiger_get_market_status

PolicyLayer is an MCP gateway — it sits between your AI agents and Tiger MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for tiger_get_market_status:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "tiger_get_market_status": {}
  }
}

tiger_get_market_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Tiger MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about tiger_get_market_status

What does the tiger_get_market_status tool do? +

tiger_get_market_status. It is categorised as a Read tool in the Tiger MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on tiger_get_market_status? +

Register the Tiger MCP server in PolicyLayer and add a rule for tiger_get_market_status: 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 Tiger MCP. Nothing to install.

What risk level is tiger_get_market_status? +

tiger_get_market_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit tiger_get_market_status? +

Yes. Add a rate_limit block to the tiger_get_market_status 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.

How do I block tiger_get_market_status completely? +

Set action: deny in the PolicyLayer policy for tiger_get_market_status. 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.

What MCP server provides tiger_get_market_status? +

tiger_get_market_status is provided by the Tiger MCP server (luxiaolei/tiger-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Tiger MCP tool call.

Start from Tiger 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.

23 Tiger MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.