code_stats
Get code statistics: LOC, comments, blank lines, functions, classes.
This record as markdown: /tools/io-github-scotia1973-bot-api-hub/code-stats.md
What code_stats does on GadgetHumans API Hub
AI agents call code_stats to retrieve information from GadgetHumans API Hub without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why code_stats is rated Low
This tool queries code to extract statistical metadata. It has no side effects, cannot execute code, modify state, or destroy data. It purely reads and reports analysis results, consistent with the Read category.
From the tool's definition Tool description states 'Get code statistics' — a retrieval operation that analyzes and reports metrics (LOC, comments, blank lines, functions, classes) without modifying, executing, or deleting data.
Attacks that exploit this kind of access
The rule that runs code_stats safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GadgetHumans API Hub, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For code_stats, this is the rule to start with:
code_stats 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 GadgetHumans API Hub, apply this rule, and every code_stats call is checked against it from then on.
Questions about code_stats
Get code statistics: LOC, comments, blank lines, functions, classes. It is categorised as a Read tool in the GadgetHumans API Hub MCP Server, which means it retrieves data without modifying state.
Register the GadgetHumans API Hub MCP server in PolicyLayer and add a rule for code_stats: 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 GadgetHumans API Hub. Nothing to install.
code_stats 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 code_stats 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 code_stats. 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.
code_stats is provided by the GadgetHumans API Hub MCP server (pypi:gadgethumans-api-hub-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GadgetHumans API Hub, and thousands of servers like it.
This server
Across the catalogue