Use this read-only tool when agents need the complete ATLAS-7 calculation bundle for an issuer and source_date. It assembles one calculation-history row from the existing ATLAS-7 precomputed surfaces: covenant stress, company fundamentals, peer ranking, alpha signals, alpha score breakdown, marke...
Part of the DeltaSignal ATLAS-7 server.
Free to start. No card required.
AI agents call deltasignal_atlas7_calculation_history 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_atlas7_calculation_history 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_atlas7_calculation_history": {}
}
}See the full DeltaSignal ATLAS-7 policy for all 33 tools.
These attack patterns abuse exactly the kind of access deltasignal_atlas7_calculation_history 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 tool when agents need the complete ATLAS-7 calculation bundle for an issuer and source_date. It assembles one calculation-history row from the existing ATLAS-7 precomputed surfaces: covenant stress, company fundamentals, peer ranking, alpha signals, alpha score breakdown, market regime context, SPECTRA inputs, quality flags, provenance, source fields, and hashes. Parameters: source_date replays one YYYY-MM-DD ATLAS-7 slice; source_date_from/source_date_to can page recent slices; ticker or CIK narrows to one issuer; mode=compact by default and full includes source_fields_json. Behavior: read-only and idempotent; it has no destructive side effects and performs no wallet, settlement, or trading actions. Use this before historical report rendering so agents do not mix latest-only fields into a historical answer.. 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_atlas7_calculation_history: 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_atlas7_calculation_history 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_atlas7_calculation_history 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_atlas7_calculation_history. 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_atlas7_calculation_history 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.