return_content
Returns actual log content instead of URLs (boolean, optional)
This record as markdown: /tools/io-github-aifity-omnigit-mcp/return-content.md
What return_content does on GitHub
AI agents call return_content to retrieve information from GitHub without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why return_content is rated Low
This is a data retrieval tool that fetches log content. It has no side effects—it only changes the format of returned information (content vs. URLs). No creation, modification, deletion, or code execution occurs. The low severity reflects minimal blast radius: an AI agent misusing this would only retrieve log data already accessible through normal GitHub operations.
From the tool's definition Tool name 'return_content' and description indicate this retrieves or returns log content data. No modification, deletion, or execution capability is described.
Attacks that exploit this kind of access
The rule that runs return_content safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GitHub, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For return_content, this is the rule to start with:
return_content 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 GitHub, apply this rule, and every return_content call is checked against it from then on.
Questions about return_content
Returns actual log content instead of URLs (boolean, optional). It is categorised as a Read tool in the GitHub MCP Server, which means it retrieves data without modifying state.
Register the GitHub MCP server in PolicyLayer and add a rule for return_content: 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 GitHub. Nothing to install.
return_content 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 return_content 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 return_content. 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.
return_content is provided by the GitHub MCP server (oci:ghcr.io/aifity/omnigit-mcp:0.5.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GitHub, and thousands of servers like it.
This server
Across the catalogue