Return the union of all asset symbols supported by MAXIA Oracle,
AI agents call list_supported_symbols to retrieve information from OracleForge MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns a list of supported asset symbols. It is a query operation that does not create, modify, delete, or execute any operations. The only potential side effect is reading from a cache or database, which is a standard Read operation. The blast radius is minimal as it only exposes metadata about available assets.
From the tool's definition Tool name 'list_supported_symbols' and description 'Return the union of all asset symbols supported by MAXIA Oracle' indicate a simple data retrieval operation with no modifications or side effects.
Attacks that exploit this kind of access
Return the union of all asset symbols supported by MAXIA Oracle,. It is categorised as a Read tool in the OracleForge MCP MCP Server, which means it retrieves data without modifying state.
Register the OracleForge MCP server in PolicyLayer and add a rule for list_supported_symbols: 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 OracleForge MCP. Nothing to install.
list_supported_symbols 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 list_supported_symbols 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 list_supported_symbols. 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.
list_supported_symbols is provided by the OracleForge MCP server (maxiaworld/oracleforge). 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 →