snow_report_manage
Unified tool for ServiceNow report lifecycle beyond creation: list, get, run, schedule, share, and export. Wraps sys_report, sysauto_report, and sys_report_users_groups. Actions: - list — list sys_report definitions, optionally filtered by table or owner - get — retrieve a single report (sys_id o...
This record as markdown: /tools/serac/snow-report-manage.md
What snow_report_manage does on Serac
AI agents invoke snow_report_manage to trigger actions in Serac. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why snow_report_manage is rated High
While some actions (list, get) are Read, the most severe applicable category is Execute because 'run' triggers ad-hoc report execution and 'schedule' creates or modifies scheduled automation jobs. 'Share' and 'export' also have Write-level side effects. Per the rules, we pick the most severe applicable category across all actions, which is Execute due to the ad-hoc execution and scheduling of automated jobs.
From the tool's definition Actions include: run — execute the report ad-hoc and return rows; schedule — create or update a sysauto_report row; share — share a report with users or groups; export — export the report
Attacks that exploit this kind of access
The rule that runs snow_report_manage safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Serac, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For snow_report_manage, this is the rule to start with:
snow_report_manage stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Serac, apply this rule, and every snow_report_manage call is checked against it from then on.
Questions about snow_report_manage
Unified tool for ServiceNow report lifecycle beyond creation: list, get, run, schedule, share, and export. Wraps sys_report, sysauto_report, and sys_report_users_groups. Actions: - list — list sys_report definitions, optionally filtered by table or owner - get — retrieve a single report (sys_id or title) - run — execute the report ad-hoc and return rows from the configured table using the report filter - schedule — create or update a sysauto_report row (recurrence, time, recipients) - share — share a report with users or groups via sys_report_users_groups - export — export the report. It is categorised as a Execute tool in the Serac MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Serac MCP server in PolicyLayer and add a rule for snow_report_manage: 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 Serac. Nothing to install.
snow_report_manage is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the snow_report_manage 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 snow_report_manage. 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.
snow_report_manage is provided by the Serac MCP server (serac-labs/serac). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Serac, and thousands of servers like it.
Across the catalogue