Onboarding tour for mrmarket.ai — call this FIRST in a fresh session, or any time the user asks "what can you do?" / "how does this work?". Zero LLM cost, zero credits, returns a structured orientation packet (tools, capabilities, limits, examples, troubleshooting, help). Default scope ('overview...
Part of the Mrmarket Ai server.
Free to start. No card required.
AI agents call getting_started to retrieve information from Mrmarket Ai without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though getting_started only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"getting_started": {}
}
}See the full Mrmarket Ai policy for all 8 tools.
These attack patterns abuse exactly the kind of access getting_started gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Onboarding tour for mrmarket.ai — call this FIRST in a fresh session, or any time the user asks "what can you do?" / "how does this work?". Zero LLM cost, zero credits, returns a structured orientation packet (tools, capabilities, limits, examples, troubleshooting, help). Default scope ('overview') covers everything in a short tour. Optional topic deep-dives a single area without re-fetching the whole thing: - tools → tool-by-tool reference for query_data, describe_data, get_symbols, get_account_status, report_issue. - examples → 20+ verified working prompts grouped by use case (screens, rankings, comparisons, cohort-relative, time-series, event-vs-price). - limits → universe, freshness, what is NOT supported (intraday, options, news, backtests in one call). - cost → credit model, which tools are free, how to read credits_remaining. - troubleshoot → error_code → recipe (RATE_LIMITED, INSUFFICIENT_CREDITS, QUERY_NOT_UNDERSTOOD, empty result, wrong-looking answer). - help → links + how to reach support; preferred channel is report_issue. Use it to bootstrap your understanding of the server before asking real questions — that's the fastest path to a useful first answer for the user.. It is categorised as a Read tool in the Mrmarket Ai MCP Server, which means it retrieves data without modifying state.
Register the Mrmarket Ai MCP server in PolicyLayer and add a rule for getting_started: 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 Mrmarket Ai. Nothing to install.
getting_started 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 getting_started 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 getting_started. 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.
getting_started is provided by the Mrmarket Ai MCP server (https://mcp.mrmarket.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 Mrmarket Ai tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.