sharia_compliance_screener
Sharia compliance screening engine for Islamic banks, Sukuk issuers, Gulf sovereign funds, halal investment managers and MENA family offices. Zero competing MCP on this vertical. Standards supported: AAOIFI (default) | MSCI_Islamic | S&P_Sharia | DJIM Four modes: • company — Full Sharia screen of...
This record as markdown: /tools/io-github-getgapup-mcp-knowledge/sharia-compliance-screener.md
What sharia_compliance_screener does on Mcp Knowledge
AI agents call sharia_compliance_screener to retrieve information from Mcp Knowledge without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
mode | string | Yes | Screening mode. company=full listed company screen, instrument=Sukuk/fund classification, sector_screen=industry halal/haram classification, financial_ratios=AA |
async | boolean | — | If true, returns a job_id immediately (<200ms) instead of waiting for the result. Poll the result with job_result(job_id). Use for slow tools to avoid client ti |
query | string | Yes | Entity to screen. Company name, ticker or ISIN (e.g. "Aramco", "AAPL", "tobacco", "XS1234567890"). |
standard | string | — | Sharia standard to apply. Default "AAOIFI" (most conservative, widely accepted by Islamic banks). |
Parameters from the server's own tool schema.
Why sharia_compliance_screener is rated Low
This tool performs compliance screening and classification — it retrieves and analyzes data about companies, instruments, and sectors against Sharia standards. There is no indication it creates, modifies, executes, or deletes data; it reads and evaluates existing financial/business information.
From the tool's definition Sharia compliance screening engine... Full Sharia screen of a listed company: business activity (halal/haram/mixed) + AAOIFI financial ratios... instrument — Sukuk / halal fund classification by ISIN or name... sector_screen — Industry classification
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
The rule that runs sharia_compliance_screener safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Knowledge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sharia_compliance_screener, this is the rule to start with:
sharia_compliance_screener is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Knowledge, apply this rule, and every sharia_compliance_screener call is checked against it from then on.
Questions about sharia_compliance_screener
Sharia compliance screening engine for Islamic banks, Sukuk issuers, Gulf sovereign funds, halal investment managers and MENA family offices. Zero competing MCP on this vertical. Standards supported: AAOIFI (default) | MSCI_Islamic | S&P_Sharia | DJIM Four modes: • company — Full Sharia screen of a listed company: business activity (halal/haram/mixed) + AAOIFI financial ratios (debt/market-cap <30%, interest-assets <30%, non-compliant revenue <5%) • instrument — Sukuk / halal fund classification by ISIN or name. Maps to known Sharia boards. • sector_screen — Industry classification (halal/haram/mixed) with rationale + examples. Static AAOIFI-based map covering 40+ sectors. • financial_ratios — AAOIFI ratio computation on fetched or provided financials. Prohibited activities screened: alcohol, gambling, pork, weapons, pornography, tobacco, conventional banking (riba), conventional insurance, adult entertainment, embryonic stem cells. Output includes compliance_status (halal/haram/doubtful_mixed/purification_required), purification_pct when applicable, P0/P1/P2 signals, quality_score, and sources. It is categorised as a Read tool in the Mcp Knowledge MCP Server, which means it retrieves data without modifying state.
sharia_compliance_screener accepts 4 parameters: mode, async, query, standard. Required: mode, query. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Knowledge MCP server in PolicyLayer and add a rule for sharia_compliance_screener: 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 Mcp Knowledge. Nothing to install.
sharia_compliance_screener 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 sharia_compliance_screener 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 sharia_compliance_screener. 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.
sharia_compliance_screener is provided by the Mcp Knowledge MCP server (https://mcp.gapup.io). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Knowledge, and thousands of servers like it.
This server
Across the catalogue