get_rugsense_track_record
The leakage-free scoreboard of every RugSense verdict: avoid.precisionPct = share of resolved
This record as markdown: /tools/0xcnr0-rugsense/get-rugsense-track-record.md
What get_rugsense_track_record does on RugSense
AI agents call get_rugsense_track_record to retrieve information from RugSense without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_rugsense_track_record is rated Low
This is a read-only query operation that retrieves historical verdict accuracy data. It neither modifies data, executes operations, deletes information, nor involves financial transactions. The low severity reflects that retrieving historical scoring accuracy poses minimal risk even if misused by an agent.
From the tool's definition Tool name 'get_rugsense_track_record' and description indicate it retrieves/queries a 'scoreboard of every RugSense verdict' showing historical accuracy metrics ('avoid.precisionPct').
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs get_rugsense_track_record safely
PolicyLayer is an MCP gateway: it sits between your AI agents and RugSense, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_rugsense_track_record, this is the rule to start with:
get_rugsense_track_record 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 RugSense, apply this rule, and every get_rugsense_track_record call is checked against it from then on.
Questions about get_rugsense_track_record
The leakage-free scoreboard of every RugSense verdict: avoid.precisionPct = share of resolved. It is categorised as a Read tool in the RugSense MCP Server, which means it retrieves data without modifying state.
Register the RugSense MCP server in PolicyLayer and add a rule for get_rugsense_track_record: 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 RugSense. Nothing to install.
get_rugsense_track_record 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 get_rugsense_track_record 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 get_rugsense_track_record. 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.
get_rugsense_track_record is provided by the RugSense MCP server (0xcnr0/rugsense). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on RugSense, and thousands of servers like it.
This server
Across the catalogue