get_turboquant_last_scan_stats

A read tool on the Mcpg MCP server.

SERVERMcpg SOURCEpypi:mcpg
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-devopam-mcpg/get-turboquant-last-scan-stats.md

What get_turboquant_last_scan_stats does on Mcpg

AI agents call get_turboquant_last_scan_stats to retrieve information from Mcpg without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_turboquant_last_scan_stats is rated Low

The tool name strongly indicates a read operation that retrieves scan statistics. The 'get_' prefix is characteristic of query/retrieval functions. No evidence of side effects, data mutation, or destructive operations. In the context of a PostgreSQL MCP server, this appears to be a diagnostic or monitoring tool that queries existing statistics. Low severity as it merely accesses data.

From the tool's definition Tool name 'get_turboquant_last_scan_stats' contains 'get' and 'stats', suggesting retrieval of metrics or statistics without modification. Description is empty, reducing confidence.

Questions about get_turboquant_last_scan_stats

What does the get_turboquant_last_scan_stats tool do? +

get_turboquant_last_scan_stats is a read tool on the Mcpg MCP server. It is categorised as a Read tool in the Mcpg MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_turboquant_last_scan_stats? +

Register the Mcpg MCP server in PolicyLayer and add a rule for get_turboquant_last_scan_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 Mcpg. Nothing to install.

What risk level is get_turboquant_last_scan_stats? +

get_turboquant_last_scan_stats is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_turboquant_last_scan_stats? +

Yes. Add a rate_limit block to the get_turboquant_last_scan_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.

How do I block get_turboquant_last_scan_stats completely? +

Set action: deny in the PolicyLayer policy for get_turboquant_last_scan_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.

What MCP server provides get_turboquant_last_scan_stats? +

get_turboquant_last_scan_stats is provided by the Mcpg MCP server (pypi:mcpg). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Mcpg, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Mcpg's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.