Critical Risk →

stix-feed-summary

Live shape report on the DugganUSA STIX 2.1 threat feed for a chosen lookback window (1-7 days). Returns total indicator count, top malware families, top source feeds, type breakdown (ip/domain/url/hash/cidr), and top countries. Use this BEFORE pulling the full STIX bundle to gauge feed depth and...

Part of the Jeevesus — DugganUSA Threat Intelligence MCP server.

stix-feed-summary can permanently delete data in Jeevesus — DugganUSA Threat Intelligence MCP, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE JEEVESUS — DUGGANUSA THREAT INTELLIGENCE MCP →

Free to start. No card required.

AI agents may call stix-feed-summary to permanently remove or destroy resources in Jeevesus — DugganUSA Threat Intelligence MCP. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call stix-feed-summary in a loop, permanently destroying resources in Jeevesus — DugganUSA Threat Intelligence MCP. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "stix-feed-summary"
  ]
}

See the full Jeevesus — DugganUSA Threat Intelligence MCP policy for all 3 tools.

Get this rule live on your own Jeevesus — DugganUSA Threat Intelligence MCP server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY JEEVESUS — DUGGANUSA THREAT INTELLIGENCE MCP →

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

SECURE JEEVESUS — DUGGANUSA THREAT INTELLIGENCE MCP →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the stix-feed-summary tool do? +

Live shape report on the DugganUSA STIX 2.1 threat feed for a chosen lookback window (1-7 days). Returns total indicator count, top malware families, top source feeds, type breakdown (ip/domain/url/hash/cidr), and top countries. Use this BEFORE pulling the full STIX bundle to gauge feed depth and freshness, plan SIEM ingestion budget, or sanity-check that a campaign you read about is actually in our corpus. Does NOT return the full bundle — for that, fetch https://analytics.dugganusa.com/api/v1/stix-feed with the same Bearer key. The bundle is STIX 2.1 / TAXII 2.1 with Splunk ES, OPNsense, Suricata, and Unbound DNS sinkhole plugins. Authentication required (Bearer token). Anonymous callers get a clear 401 with the registration URL. Example: {"days": 7} returns the last week's feed shape — useful for capacity planning and spot-checking recent ingest tags.. It is categorised as a Destructive tool in the Jeevesus — DugganUSA Threat Intelligence MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on stix-feed-summary? +

Register the Jeevesus — DugganUSA Threat Intelligence MCP server in PolicyLayer and add a rule for stix-feed-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 Jeevesus — DugganUSA Threat Intelligence MCP. Nothing to install.

What risk level is stix-feed-summary? +

stix-feed-summary is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit stix-feed-summary? +

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

Set action: deny in the PolicyLayer policy for stix-feed-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 stix-feed-summary? +

stix-feed-summary is provided by the Jeevesus — DugganUSA Threat Intelligence MCP server (https://analytics.dugganusa.com/api/v1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Jeevesus — DugganUSA Threat Intelligence MCP tool call.

Deterministic rules across all 3 Jeevesus — DugganUSA Threat Intelligence 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.