测试工具
AI agents call test as a supporting operation in Stock Analysis MCP Server workflows.
The name and description provide no meaningful information about what this tool does. 'Test tool' could be a simple health check or ping with no side effects. Given the server context (stock analysis/read-only data), it is unlikely to be destructive or financial, but confidence is low due to the uninformative description. Defaulting to Other with low severity.
From the tool's definition Tool name is 'test' and description is '测试工具' (meaning 'test tool' in Chinese) — uninformative about actual behavior.
Attacks that exploit this kind of access
测试工具. It is categorised as a Other tool in the Stock Analysis MCP Server MCP Server, which means it performs auxiliary operations.
Register the Stock Analysis MCP Server MCP server in PolicyLayer and add a rule for test: 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 Stock Analysis MCP Server. Nothing to install.
test is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the test 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 test. 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.
test is provided by the Stock Analysis MCP Server MCP server (kore-01/mcp590). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →