Use this read-only drilldown tool only when the user asks why one issuer or CIK was flagged in daily changes. It returns paginated raw CompanyFacts tag evidence for a specific ticker or CIK, plus page metadata and issuer identity. Parameters: ticker or cik is required; source_date is optional; li...
Part of the DeltaSignal ATLAS-7 server.
Free to start. No card required.
AI agents call deltasignal_daily_change_evidence to retrieve information from DeltaSignal ATLAS-7 without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though deltasignal_daily_change_evidence only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"deltasignal_daily_change_evidence": {}
}
}See the full DeltaSignal ATLAS-7 policy for all 33 tools.
These attack patterns abuse exactly the kind of access deltasignal_daily_change_evidence gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Use this read-only drilldown tool only when the user asks why one issuer or CIK was flagged in daily changes. It returns paginated raw CompanyFacts tag evidence for a specific ticker or CIK, plus page metadata and issuer identity. Parameters: ticker or cik is required; source_date is optional; limit defaults to 100 and is capped at 250; offset paginates the raw tag page. Behavior: read-only and idempotent; it performs one internal daily-changes read, filters evidence for one issuer/change, and has no destructive side effects. Do not use it for routine monitoring, Morning Brief, or Alpha Sweep unless the user explicitly asks for proof.. It is categorised as a Read tool in the DeltaSignal ATLAS-7 MCP Server, which means it retrieves data without modifying state.
Register the DeltaSignal ATLAS-7 MCP server in PolicyLayer and add a rule for deltasignal_daily_change_evidence: 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 DeltaSignal ATLAS-7. Nothing to install.
deltasignal_daily_change_evidence 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 deltasignal_daily_change_evidence 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 deltasignal_daily_change_evidence. 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.
deltasignal_daily_change_evidence is provided by the DeltaSignal ATLAS-7 MCP server (https://api.aitrailblazer.net/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 33 DeltaSignal ATLAS-7 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.