Persist an alert and register it with the firing pipeline. Three condition shapes: * filing_event — fire when a ticker files a chosen form type (8-K, 10-K, etc.). * ratio_threshold — fire when a ticker's financial ratio crosses a threshold (e.g. interest_coverage < 1.5). * watchlist_change — fire...
Risk signalsBulk/mass operation — affects multiple targets
Part of the Valuein — SEC EDGAR Fundamentals & Smart-Money Data server.
Free to start. No card required.
AI agents use create_alert to create or modify resources in Valuein — SEC EDGAR Fundamentals & Smart-Money Data. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call create_alert repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Valuein — SEC EDGAR Fundamentals & Smart-Money Data.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"create_alert": {
"limits": [
{
"counter": "create_alert_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} See the full Valuein — SEC EDGAR Fundamentals & Smart-Money Data policy for all 68 tools.
These attack patterns abuse exactly the kind of access create_alert gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Persist an alert and register it with the firing pipeline. Three condition shapes: * filing_event — fire when a ticker files a chosen form type (8-K, 10-K, etc.). * ratio_threshold — fire when a ticker's financial ratio crosses a threshold (e.g. interest_coverage < 1.5). * watchlist_change — fire on any filing on any ticker in a named watchlist. Delivery channels: email (transactional via Resend) or webhook (HMAC-SHA256-signed POST). The cron evaluator runs every 5 minutes. Use test_alert to verify your channel is wired correctly before relying on the cron.. It is categorised as a Write tool in the Valuein — SEC EDGAR Fundamentals & Smart-Money Data MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Valuein — SEC EDGAR Fundamentals & Smart-Money Data MCP server in PolicyLayer and add a rule for create_alert: 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 Valuein — SEC EDGAR Fundamentals & Smart-Money Data. Nothing to install.
create_alert is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_alert 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 create_alert. 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.
create_alert is provided by the Valuein — SEC EDGAR Fundamentals & Smart-Money Data MCP server (https://mcp.valuein.biz/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 68 Valuein — SEC EDGAR Fundamentals & Smart-Money Data 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.