Get real-time 5-second bid/ask and transaction statistics
AI agents call getFiveSecondStats to retrieve information from TWSE MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries market statistics (bid/ask spreads and transaction data) with no side effects. It falls squarely in the Read category as a data retrieval operation. The severity is low because misuse by an AI agent would only result in unwanted information access, not operational harm, financial loss, or data modification.
From the tool's definition Tool name 'getFiveSecondStats' and description 'Get real-time 5-second bid/ask and transaction statistics' indicate data retrieval only. No modification, execution, deletion, or financial transaction capability is present.
Attacks that exploit this kind of access
Get real-time 5-second bid/ask and transaction statistics. It is categorised as a Read tool in the TWSE MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TWSE MCP Server MCP server in PolicyLayer and add a rule for getFiveSecondStats: 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 TWSE MCP Server. Nothing to install.
getFiveSecondStats 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 getFiveSecondStats 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 getFiveSecondStats. 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.
getFiveSecondStats is provided by the TWSE MCP Server MCP server (pyang2045/twsemcp). 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 →