AI agents call graph_edges 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 name 'graph_edges' indicates a query or retrieval function that returns edge data from a graph structure. Without a description, confidence is moderate; however, 'edges' implies read-only access to graph relationships. The context (Novyx governance/audit system) and sibling tools (audit, action_history, action_status) suggest this likely queries stored data rather than modifying or executing operations.
From the tool's definition Tool name 'graph_edges' suggests retrieval of graph structure data (edges). No description provided to confirm behavior, but the name pattern aligns with query/retrieval operations common in graph databases or knowledge graphs.
Documented attack patterns abuse exactly the kind of access graph_edges 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 graph_edges:
{
"version": "1",
"default": "deny",
"tools": {
"graph_edges": {}
}
}graph_edges 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.
graph_edges. 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 graph_edges: 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.
graph_edges 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 graph_edges 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 graph_edges. 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.
graph_edges 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.