list_tool_constants

List valid constants for tool parameters.

SERVERA-Share MCP Server SOURCE24mlight/a-share-mcp-is-just-i-need

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade A, identity unverified Pull the record →

This record as markdown: /tools/24mlight-a-share-mcp-is-just-i-need/list-tool-constants.md

WHAT IT DOES

What list_tool_constants does on A-Share MCP Server

AI agents call list_tool_constants to retrieve information from A-Share MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_tool_constants is rated Low

This tool simply returns reference information (valid parameter constants) for configuring other tools. It is a metadata query with no side effects, no code execution, no data modification, and no access to actual market or financial data. It falls squarely into the 'Read' category as a lookup/list operation.

From the tool's definition Tool name 'list_tool_constants' and description 'List valid constants for tool parameters' indicate a retrieval operation that enumerates metadata about tool parameters without modifying, executing, or accessing sensitive market data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_tool_constants safely

PolicyLayer is an MCP gateway: it sits between your AI agents and A-Share MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_tool_constants, this is the rule to start with:

list_tool_constants Allowed

list_tool_constants is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_tool_constants": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect A-Share MCP Server, apply this rule, and every list_tool_constants call is checked against it from then on.

FAQ

Questions about list_tool_constants

What does the list_tool_constants tool do? +

List valid constants for tool parameters. It is categorised as a Read tool in the A-Share MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_tool_constants? +

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

What risk level is list_tool_constants? +

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

Can I rate-limit list_tool_constants? +

Yes. Add a rate_limit block to the list_tool_constants 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 list_tool_constants completely? +

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

list_tool_constants is provided by the A-Share MCP Server MCP server (24mlight/a-share-mcp-is-just-i-need). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on A-Share MCP Server, and thousands of servers like it.

This server

All 41 A-Share MCP Server tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →