Low Risk

query_triples

query_triples

How to control query_triples ↓

AI agents call query_triples 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.

Low Risk

Query operations retrieve or fetch data without modifying, deleting, or executing code. Despite the empty description lowering confidence slightly, the naming pattern and sibling tools (audit, action_history, add_triple) suggest this tool retrieves stored triples from shared memory rather than executing arbitrary operations. No destructive, financial, or code execution capability is implied.

From the tool's definition Tool name 'query_triples' indicates a query operation, which retrieves data. Description is empty, but the sibling context shows this is part of a governance and audit system that manages triples (likely semantic knowledge), and querying typically has no side…

Documented attack patterns abuse exactly the kind of access query_triples 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 query_triples:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "query_triples": {}
  }
}

query_triples is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Novyx — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the query_triples tool do? +

query_triples. It is categorised as a Read tool in the Novyx MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on query_triples? +

Register the Novyx MCP server in PolicyLayer and add a rule for query_triples: 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.

What risk level is query_triples? +

query_triples is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit query_triples? +

Yes. Add a rate_limit block to the query_triples 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.

How do I block query_triples completely? +

Set action: deny in the PolicyLayer policy for query_triples. 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.

What MCP server provides query_triples? +

query_triples 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.

Enforce policy on every Novyx tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.