Get top ETFs by regular investment accounts
AI agents call getETFRanking 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 ranks ETF data without creating, modifying, deleting, or executing external operations. It has no side effects on data or financial positions. While the server provides financial market data, this specific tool performs pure read operations on published market information, posing minimal risk if invoked by an AI agent.
From the tool's definition Tool name 'getETFRanking' and description 'Get top ETFs by regular investment accounts' indicate data retrieval without modification. The verb 'Get' and the passive framing show this retrieves or queries ETF ranking information.
Attacks that exploit this kind of access
Get top ETFs by regular investment accounts. 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 getETFRanking: 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.
getETFRanking 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 getETFRanking 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 getETFRanking. 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.
getETFRanking 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 →