AI agents call get_limit_list to retrieve information from Tushare MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on the tool name and context of the Tushare server (financial data queries), this appears to be a data retrieval operation. The 'get_' prefix and lack of action words like 'create', 'delete', 'execute' suggest read-only access. The empty description lowers confidence slightly, but the pattern of sibling tools all being data retrieval functions supports the Read classification.
From the tool's definition Tool name 'get_limit_list' suggests retrieval of limit-related data (e.g., daily price limits, trading limits) from Tushare API.
Documented attack patterns abuse exactly the kind of access get_limit_list gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Tushare MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_limit_list:
{
"version": "1",
"default": "deny",
"tools": {
"get_limit_list": {}
}
}get_limit_list 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.
get_limit_list. It is categorised as a Read tool in the Tushare MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Tushare MCP Server MCP server in PolicyLayer and add a rule for get_limit_list: 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 Tushare MCP Server. Nothing to install.
get_limit_list 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 get_limit_list 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 get_limit_list. 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.
get_limit_list is provided by the Tushare MCP Server MCP server (zhewenzhang/tushare_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 66 Tushare MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
66 Tushare MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.