get_surface
Return the market-implied probability surface for gold or silver — what the options market (GLD/SLV chains) and the prediction markets (Kalshi, Polymarket) jointly imply about where the metal is going. metal is xau or xag; optional horizon is an ISO date from the expiries index. One call returns ...
This record as markdown: /tools/dev-goldprice-mcp/get-surface.md
What get_surface does on Goldprice Dev
AI agents call get_surface to retrieve information from Goldprice Dev without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
metal | string | Yes | |
horizon | object | — |
Parameters from the server's own tool schema.
Why get_surface is rated Low
This is a read-only data retrieval tool that queries and returns financial market data (options-implied probabilities and prediction market information). It has no side effects, does not execute trades or commands, does not modify data, and does not commit financial obligations.
From the tool's definition Tool returns market-implied probability surfaces and analysis data from options and prediction markets. Language: 'Return the market-implied probability surface', 'returns per-venue probability curves', 'gated consensus'.
Attacks that exploit this kind of access
The rule that runs get_surface safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Goldprice Dev, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_surface, this is the rule to start with:
get_surface is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Goldprice Dev, apply this rule, and every get_surface call is checked against it from then on.
Questions about get_surface
Return the market-implied probability surface for gold or silver — what the options market (GLD/SLV chains) and the prediction markets (Kalshi, Polymarket) jointly imply about where the metal is going. metal is xau or xag; optional horizon is an ISO date from the expiries index. One call returns per-venue probability curves, a gated consensus, the options-vs-PM wedge, and touch markets. Requires the Pro tier or higher; static sample responses for evaluation are in the docs at https://goldprice.dev/docs/surface. It is categorised as a Read tool in the Goldprice Dev MCP Server, which means it retrieves data without modifying state.
get_surface accepts 2 parameters: metal, horizon. Required: metal. The full parameter table on this page comes from the server's own tool schema.
Register the Goldprice Dev MCP server in PolicyLayer and add a rule for get_surface: 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 Goldprice Dev. Nothing to install.
get_surface 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 get_surface 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 get_surface. 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.
get_surface is provided by the Goldprice Dev MCP server (https://api.goldprice.dev/v1/mcp/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Goldprice Dev, and thousands of servers like it.
This server
Across the catalogue