Low Risk

portfolio_analyze

Compute PnL + risk assessment for a portfolio you own. Returns per-holding pnl, risk_assessment, and top_risks.

Part of the Marketintell server.

portfolio_analyze is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE MARKETINTELL →

Free to start. No card required.

AI agents call portfolio_analyze to retrieve information from Marketintell 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 portfolio_analyze 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "portfolio_analyze": {}
  }
}

See the full Marketintell policy for all 17 tools.

Get this rule live on your own Marketintell server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY MARKETINTELL →

View all 17 tools →

These attack patterns abuse exactly the kind of access portfolio_analyze gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so portfolio_analyze only ever does what you allow.

SECURE MARKETINTELL →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the portfolio_analyze tool do? +

Compute PnL + risk assessment for a portfolio you own. Returns per-holding pnl, risk_assessment, and top_risks.. It is categorised as a Read tool in the Marketintell MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on portfolio_analyze? +

Register the Marketintell MCP server in PolicyLayer and add a rule for portfolio_analyze: 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 Marketintell. Nothing to install.

What risk level is portfolio_analyze? +

portfolio_analyze is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit portfolio_analyze? +

Yes. Add a rate_limit block to the portfolio_analyze 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.

How do I block portfolio_analyze completely? +

Set action: deny in the PolicyLayer policy for portfolio_analyze. 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.

What MCP server provides portfolio_analyze? +

portfolio_analyze is provided by the Marketintell MCP server (marketintell). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Marketintell tool call.

Deterministic rules across all 17 Marketintell 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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.