sanctions_status_summary

Counts and last-update timestamps for all four lists in the cache. No screening is performed; this call is free.

SERVERLivedatalink SOURCEhttps://livedatalink.ai/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/sanctions-status-summary.md

WHAT IT DOES

What sanctions_status_summary does on Livedatalink

AI agents call sanctions_status_summary to retrieve information from Livedatalink without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why sanctions_status_summary is rated Low

This tool queries aggregate statistics about sanctions data (counts and timestamps) without side effects. It is purely informational retrieval, making it a Read operation. The low severity reflects minimal risk—miscalling this tool causes no harm beyond receiving aggregate information. High confidence due to clear description indicating passive data retrieval only.

From the tool's definition Tool performs 'counts and last-update timestamps' lookup with 'no screening' performed. Retrieves cached metadata about sanctions lists without modification or execution of external operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs sanctions_status_summary safely

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

sanctions_status_summary Allowed

sanctions_status_summary 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": {
    "sanctions_status_summary": {}
  }
}

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

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

FAQ

Questions about sanctions_status_summary

What does the sanctions_status_summary tool do? +

Counts and last-update timestamps for all four lists in the cache. No screening is performed; this call is free. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on sanctions_status_summary? +

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

What risk level is sanctions_status_summary? +

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

Can I rate-limit sanctions_status_summary? +

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

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

sanctions_status_summary is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Livedatalink, and thousands of servers like it.

This server

All 280 Livedatalink tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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