security_fetch_cve_watch_status
Check all specified CVE watches for new events since your last poll. Returns only watches with new events, making it efficient to run on a schedule. watch_ids: List of watch IDs to check — same IDs used when creating watches with security_fetch_cve_watch. Required. Uses a per-user cursor (last_po...
This record as markdown: /tools/dev-7bd0-mcp-server/security-fetch-cve-watch-status.md
What security_fetch_cve_watch_status does on DataNexus MCP
AI agents call security_fetch_cve_watch_status to retrieve information from DataNexus MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
watch_ids | array | — | List of watch IDs to check e.g. ['watch-1','watch-2']. Required. |
Parameters from the server's own tool schema.
Why security_fetch_cve_watch_status is rated Low
This is a read-only monitoring/query operation. It fetches event data for user-specified CVE watches and returns results without creating, modifying, deleting, or executing anything. The mention of Redis storage and per-user cursors is infrastructure for tracking state, not an indication of write capability.
From the tool's definition Tool 'checks' CVE watches and 'returns' only watches with new events. No modification, deletion, or execution capability—purely retrieves event status based on polling cursors stored in Redis.
Attacks that exploit this kind of access
The rule that runs security_fetch_cve_watch_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and DataNexus MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For security_fetch_cve_watch_status, this is the rule to start with:
security_fetch_cve_watch_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect DataNexus MCP, apply this rule, and every security_fetch_cve_watch_status call is checked against it from then on.
Questions about security_fetch_cve_watch_status
Check all specified CVE watches for new events since your last poll. Returns only watches with new events, making it efficient to run on a schedule. watch_ids: List of watch IDs to check — same IDs used when creating watches with security_fetch_cve_watch. Required. Uses a per-user cursor (last_polled timestamp) stored in Redis. First call returns events from the last 30 days. Subsequent calls return only events newer than the last poll. Sources: Redis (existing watch data written by security_fetch_cve_watch). No external API calls — instant response. If this tool's response does not serve the user's need, call report_feedback with feedback_type="agent_gap", tool_id="security_fetch_cve_watch_status", intended_query="{what the user needed}", gap_description="{what was missing or wrong in the result}". It is categorised as a Read tool in the DataNexus MCP MCP Server, which means it retrieves data without modifying state.
security_fetch_cve_watch_status accepts 1 parameter: watch_ids. The full parameter table on this page comes from the server's own tool schema.
Register the DataNexus MCP server in PolicyLayer and add a rule for security_fetch_cve_watch_status: 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 DataNexus MCP. Nothing to install.
security_fetch_cve_watch_status 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 security_fetch_cve_watch_status 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 security_fetch_cve_watch_status. 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.
security_fetch_cve_watch_status is provided by the DataNexus MCP server (dev-7bd0/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on DataNexus, and thousands of servers like it.
This server
Across the catalogue