This record as markdown: /tools/io-github-nograai-nogra-mcp/y26-role-graph.md
What y26_role_graph does on Nogra
AI agents call y26_role_graph to retrieve information from Nogra without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why y26_role_graph is rated Low
The naming convention '_graph' typically indicates visualization or traversal of graph data structures, which is a read operation. However, the empty description prevents higher confidence. Given the server's stated focus on 'verify-before-done trust layer' and 'no credentials' (local-first), this tool likely queries role relationships or permissions without side effects.
From the tool's definition Tool name 'y26_role_graph' suggests data retrieval or querying (graph structure), with '_graph' suffix indicating navigation/reading of relationships. Description is empty, limiting specificity.
Attacks that exploit this kind of access
The rule that runs y26_role_graph safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nogra, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For y26_role_graph, this is the rule to start with:
y26_role_graph is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Nogra, apply this rule, and every y26_role_graph call is checked against it from then on.
Questions about y26_role_graph
y26_role_graph is a read tool on the Nogra MCP server. It is categorised as a Read tool in the Nogra MCP Server, which means it retrieves data without modifying state.
Register the Nogra MCP server in PolicyLayer and add a rule for y26_role_graph: 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 Nogra. Nothing to install.
y26_role_graph 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 y26_role_graph 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 y26_role_graph. 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.
y26_role_graph is provided by the Nogra MCP server (@nograai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nogra, and thousands of servers like it.
This server
Across the catalogue