get_sectors

THE RISK

Low Risk

Why get_sectors needs a policy

This tool retrieves sector performance information from Saudi market data, which is a passive data retrieval operation. It has no side effects, does not create or modify data, does not execute code or commands, and does not involve financial transactions.

From the tool's definition Tool name 'get_sectors' and description 'Get sector performance for the Saudi market' indicate a read-only query operation that retrieves market performance data with no mutation, deletion, or execution of arbitrary code.

Documented attack patterns abuse exactly the kind of access get_sectors gives an agent:

POLICY

How to control get_sectors

PolicyLayer is an MCP gateway — it sits between your AI agents and Sahmk, and nothing reaches the server without passing your rules. This is the rule we recommend for get_sectors:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_sectors": {}
  }
}

get_sectors is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Sahmk — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Sahmk tools

Read companies_list companies_list Read compare_symbols compare_symbols Read get_company Get a company profile for a Saudi stock, including sector, industry, fundamentals, valuati Read get_dividends Get company dividend history and yield data. Read get_financials get_financials Read get_historical get_historical Read get_market_movers Get market movers in one curated endpoint. Read get_market_summary Get the current Saudi market summary including TASI index level, change, market direction,

All 12 Sahmk tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_sectors

What does the get_sectors tool do? +

Get sector performance for the Saudi market. It is categorised as a Read tool in the Sahmk MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_sectors? +

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

What risk level is get_sectors? +

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

Can I rate-limit get_sectors? +

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

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

get_sectors is provided by the Sahmk MCP server (sahmk-sa/sahmk-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Sahmk tool call.

Start from Sahmk, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →