AI agents call action_history 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.
This tool retrieves and displays audit/history information about past actions. It has no side effects, does not execute code or commands, does not modify data, and does not delete anything. It is a straightforward query operation similar to 'list' or 'get'. The severity is low because access to historical audit logs poses minimal risk compared to tools that could execute code or modify state.
From the tool's definition Tool description states 'List recent Control actions with their status' - a read-only retrieval operation that queries historical action data without modifying or executing anything.
Documented attack patterns abuse exactly the kind of access action_history 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 action_history:
{
"version": "1",
"default": "deny",
"tools": {
"action_history": {}
}
}action_history 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.
List recent Control actions with their status. 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 action_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 Novyx. Nothing to install.
action_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 action_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 action_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.
action_history 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.