AI agents call get_agent 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 information about an agent using its ID as a parameter. It has no side effects—it queries existing data without creating, modifying, deleting, or executing anything. The governance context (audit, approval workflows) does not change the fundamental nature of this as a data retrieval operation. Blast radius is minimal: misuse would expose agent metadata but cause no operational harm.
From the tool's definition Tool name 'get_agent' with description 'Get an agent by ID' indicates a retrieval operation. The verb 'Get' and the absence of any modification, deletion, or execution language clearly signal a read-only query.
Documented attack patterns abuse exactly the kind of access get_agent 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_agent:
{
"version": "1",
"default": "deny",
"tools": {
"get_agent": {}
}
}get_agent 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 an agent 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_agent: 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_agent 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_agent 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_agent. 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_agent 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.