screen_sanctions_private

SERVERAinumbers Mcp Apps SOURCEpostoaklabs/ainumbers-mcp-apps

Low RISK CLASS

Category Read

Parameters 40 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/postoaklabs-ainumbers-mcp-apps/screen-sanctions-private.md

WHAT IT DOES

What screen_sanctions_private does on Ainumbers Mcp Apps

AI agents call screen_sanctions_private to retrieve information from Ainumbers Mcp Apps 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
`compute`	string	—	Compute mode (v0.4 Compute Binding). "auto" (default) = server for gpu:false nodes with registered kernels; "server" = force server-side; "browser" = always ret
`parent_hashes`	array	—	execution_hash values from upstream ChainGraph AP2 artifacts to chain from (sets chain.parent_hashes in the export).
`parent_tool_ids`	array	—	tool_id values matching parent_hashes, in the same order.
`policy_parameters`	object	—	Input parameters for this tool's decision function. For gpu:false nodes with a registered kernel, these are computed server-side when compute is "auto" or "serv

Parameters from the server's own tool schema.

RISK

Why screen_sanctions_private is rated Low

Screens inputs against sanctions lists without modifying data, though results inform compliance decisions.

From the tool's definition Sanctions Screen, deterministic compute node, transient inputs, no storage or logging.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs screen_sanctions_private safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Ainumbers Mcp Apps, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For screen_sanctions_private, this is the rule to start with:

screen_sanctions_private Allowed

screen_sanctions_private is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ainumbers Mcp Apps, apply this rule, and every screen_sanctions_private call is checked against it from then on.

FAQ

Questions about screen_sanctions_private

What does the screen_sanctions_private tool do? +

Private-Input Sanctions Screen: OpenChainGraph compute node (analytics_mandate). Deterministic OpenChainGraph compute node. By default (compute:"auto") inputs are computed server-side on Cloudflare Workers for gpu:false nodes with a registered kernel; compute:"browser" forces client-side execution and returns a browser delegation URL instead. gpu:true nodes always delegate to the browser. Inputs are processed transiently to compute the response and are not stored, logged, or retained. Use synthetic or anonymised inputs only. Exports an AP2 artifact with execution_hash for chain provenance. Open at: https://ainumbers.co/chaingraph/art-413-screen-sanctions-private.html FV-status (published/proven/still-trusted for this spec): /fv-status/8b5ae30d812cd234cfb6068c4ce2022f01d10f2a358979b0f0d73421e09d2543.json — a snapshot, not a subscription; this receipt verifies offline regardless of whether that file is ever fetched. It is categorised as a Read tool in the Ainumbers Mcp Apps MCP Server, which means it retrieves data without modifying state.

What parameters does screen_sanctions_private accept? +

screen_sanctions_private accepts 4 parameters: compute, parent_hashes, parent_tool_ids, policy_parameters. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on screen_sanctions_private? +

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

What risk level is screen_sanctions_private? +

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

Can I rate-limit screen_sanctions_private? +

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

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

screen_sanctions_private is provided by the Ainumbers Mcp Apps MCP server (postoaklabs/ainumbers-mcp-apps). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ainumbers Mcp Apps, and thousands of servers like it.

This server

All 689 Ainumbers Mcp Apps tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →