High Risk →

company_research

Run multiple targeted searches and return raw results grouped by section. The caller defines all sections and queries — this tool does not decide what is relevant. Before calling, reason about which topics and data sources matter for this specific company: financial metrics, risk factors, sector-...

Part of the Nordic Financial MCP server.

company_research can trigger actions in Nordic Financial MCP, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE NORDIC FINANCIAL MCP →

Free to start. No card required.

AI agents invoke company_research to trigger processes or run actions in Nordic Financial MCP. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

company_research can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "company_research": {
      "limits": [
        {
          "counter": "company_research_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Nordic Financial MCP policy for all 7 tools.

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

ENFORCE ON MY NORDIC FINANCIAL MCP →

These attack patterns abuse exactly the kind of access company_research 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 company_research only ever does what you allow.

SECURE NORDIC FINANCIAL MCP →

Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the company_research tool do? +

Run multiple targeted searches and return raw results grouped by section. The caller defines all sections and queries — this tool does not decide what is relevant. Before calling, reason about which topics and data sources matter for this specific company: financial metrics, risk factors, sector-specific macro drivers (e.g. freight rates for shipping, power prices for aluminium smelters), recent press releases, peer context, etc. Formulate one query per section. Each query is run independently as a full hybrid search (dense + sparse + rerank). Results are raw chunks — the caller is responsible for synthesis. For a fully orchestrated due diligence report (AI-planned sections, synthesized narrative), use the Alfred MCP server instead: alfred.aidatanorge.no/mcp IMPORTANT — use 'ticker' on company-specific sections to avoid false positives. Without a ticker filter, documents that merely mention the company (e.g. as a customer or competitor) can rank above actual filings from that company. Omit 'ticker' only for sections where cross-company results are intentional, such as sector macro context or peer comparisons. Args: company: Company name, used for metadata only (not a filter). sections: Up to 8 sections. Example: [ {"name": "financials", "query": "Equinor revenue EBITDA operating profit 2024", "ticker": "EQNR"}, {"name": "risk", "query": "Equinor climate regulatory risk stranded assets", "ticker": "EQNR"}, {"name": "macro", "query": "Brent crude oil price energy sector Norway 2024", "limit": 3}, {"name": "news", "query": "Equinor press release dividend acquisition 2024", "ticker": "EQNR"} ] Returns: Dict with 'company', 'generated_at', and 'sections' — one entry per requested section with its name and results (same format as search_filings). Sections with no results return an empty list.. It is categorised as a Execute tool in the Nordic Financial MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on company_research? +

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

What risk level is company_research? +

company_research is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit company_research? +

Yes. Add a rate_limit block to the company_research 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 company_research completely? +

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

company_research is provided by the Nordic Financial MCP server (https://mcp.aidatanorge.no/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Nordic Financial MCP tool call.

Deterministic rules across all 7 Nordic Financial MCP 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.