Return both RSI and Bollinger in one call. Inputs: values:number[] (oldest→newest), rsiPeriod?:number(14), bbPeriod?:number(20), bbMult?:number(2).
AI agents call ta_summary to retrieve information from CG Alpha MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs purely computational/analytical operations on supplied price data arrays, returning derived statistics. It has no side effects, does not modify any data, and does not interact with external systems beyond reading input values. Misuse potential is minimal — it can only return indicator values.
From the tool's definition 'Return both RSI and Bollinger in one call' — computes and returns technical analysis indicators (RSI and Bollinger Bands) from provided numerical input data
Attacks that exploit this kind of access
Return both RSI and Bollinger in one call. Inputs: values:number[] (oldest→newest), rsiPeriod?:number(14), bbPeriod?:number(20), bbMult?:number(2). It is categorised as a Read tool in the CG Alpha MCP MCP Server, which means it retrieves data without modifying state.
Register the CG Alpha MCP server in PolicyLayer and add a rule for ta_summary: 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 CG Alpha MCP. Nothing to install.
ta_summary 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 ta_summary 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 ta_summary. 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.
ta_summary is provided by the CG Alpha MCP server (jcf0/cg-alpha-mcp). 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 →