Get daily trading information for all listed stocks on TWSE
AI agents call getStockDaily 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 historical and current market data (daily trading information) from a public stock exchange. It has no side effects, cannot modify or delete data, does not execute code, and does not involve financial transactions. It is a straightforward read-only query of publicly available financial market data.
From the tool's definition Tool name is 'getStockDaily' with description stating it 'Get[s] daily trading information for all listed stocks on TWSE' — purely a data retrieval operation with no modification, deletion, or execution of commands.
Attacks that exploit this kind of access
Get daily trading information for all listed stocks on TWSE. 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 getStockDaily: 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.
getStockDaily 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 getStockDaily 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 getStockDaily. 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.
getStockDaily 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 →