Ask a natural language question about your repository. Uses Gitrama intelligence to provide context-aware answers. Example questions: - "Who owns the auth module?" - "Who are the top contributors?" - "When did we last change the payment logic?" - "What's the riskiest file in this repo?" - "What c...
Part of the Gitrama server.
Free to start. No card required.
AI agents call gitrama_ask to retrieve information from Gitrama without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though gitrama_ask only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"gitrama_ask": {}
}
}See the full Gitrama policy for all 15 tools.
These attack patterns abuse exactly the kind of access gitrama_ask gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Ask a natural language question about your repository. Uses Gitrama intelligence to provide context-aware answers. Example questions: - "Who owns the auth module?" - "Who are the top contributors?" - "When did we last change the payment logic?" - "What's the riskiest file in this repo?" - "What changed in the last 3 days?" - "Explain the purpose of src/utils/retry.py" - "What stream am I on?" Args: question: Natural language question about your repository. stream: Optional stream context override (wip | hotfix | review | experiment). deep: Enable full repo history access for deeper analysis.. It is categorised as a Read tool in the Gitrama MCP Server, which means it retrieves data without modifying state.
Register the Gitrama MCP server in PolicyLayer and add a rule for gitrama_ask: 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 Gitrama. Nothing to install.
gitrama_ask 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 gitrama_ask 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 gitrama_ask. 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.
gitrama_ask is provided by the Gitrama MCP server (GitramaLLC/gitrama-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 15 Gitrama tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.