AI agents call get_checkpoint to retrieve information from Novyx without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a simple data retrieval operation (get) to fetch checkpoint information by ID. This is a read-only operation with no side effects, no code execution, no data modification, and no destructive capability. The context of governance and audit suggests checkpoints are state snapshots, and retrieving them does not alter system state or trigger external actions.
From the tool's definition Tool description states 'Get a checkpoint by ID', which is a retrieval operation with no modification or deletion of data.
Documented attack patterns abuse exactly the kind of access get_checkpoint gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Novyx, and nothing reaches the server without passing your rules. This is the rule we recommend for get_checkpoint:
{
"version": "1",
"default": "deny",
"tools": {
"get_checkpoint": {}
}
}get_checkpoint is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get a checkpoint by ID. It is categorised as a Read tool in the Novyx MCP Server, which means it retrieves data without modifying state.
Register the Novyx MCP server in PolicyLayer and add a rule for get_checkpoint: 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 Novyx. Nothing to install.
get_checkpoint 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 get_checkpoint 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 get_checkpoint. 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.
get_checkpoint is provided by the Novyx MCP server (novyxlabs/novyx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 120 Novyx tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
120 Novyx tools catalogued and risk-classified — across an index of 42,500+ MCP servers.