This record as markdown: /tools/8vdx1-fundos-mcp/fundos-run-pricer.md
What fundos_run_pricer does on Fundos
AI agents invoke fundos_run_pricer to trigger actions in Fundos. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why fundos_run_pricer is rated High
This tool executes a computational operation ('run_pricer') on financial assets, which can affect fund valuations, performance metrics, and downstream decisions. While not immediately destructive or financial in itself, it performs active execution of code/algorithms whose effects depend on which asset is scored.
From the tool's definition Tool name 'fundos_run_pricer' and description 'score an asset' indicate execution of a pricing/valuation algorithm on fund assets.
Attacks that exploit this kind of access
The rule that runs fundos_run_pricer safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Fundos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fundos_run_pricer, this is the rule to start with:
fundos_run_pricer stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Fundos, apply this rule, and every fundos_run_pricer call is checked against it from then on.
Questions about fundos_run_pricer
Use this to score an asset. It is categorised as a Execute tool in the Fundos MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Fundos MCP server in PolicyLayer and add a rule for fundos_run_pricer: 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 Fundos. Nothing to install.
fundos_run_pricer is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the fundos_run_pricer 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 fundos_run_pricer. 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.
fundos_run_pricer is provided by the Fundos MCP server (8vdx1/fundos-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Fundos, and thousands of servers like it.
Across the catalogue