nogra_role_config
Read V1 role/model adapter config. Roles are functions; users choose models.
This record as markdown: /tools/io-github-nograai-nogra-mcp/nogra-role-config.md
What nogra_role_config does on Nogra
AI agents call nogra_role_config 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 nogra_role_config is rated Low
This tool retrieves configuration data about roles and model adapters without modifying, deleting, or executing any operations. It is a straightforward read operation with minimal blast radius if misused by an AI agent—at worst, an agent would learn internal configuration details, which poses low risk in a local-first, no-credentials environment.
From the tool's definition Tool name contains 'config' for reading; description explicitly states 'Read V1 role/model adapter config'. No modification, deletion, or execution capabilities indicated.
Attacks that exploit this kind of access
The rule that runs nogra_role_config 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 nogra_role_config, this is the rule to start with:
nogra_role_config 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 nogra_role_config call is checked against it from then on.
Questions about nogra_role_config
Read V1 role/model adapter config. Roles are functions; users choose models. 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 nogra_role_config: 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.
nogra_role_config 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 nogra_role_config 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 nogra_role_config. 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.
nogra_role_config 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