This record as markdown: /tools/io-github-devopam-mcpg/create-turboquant-index.md
What create_turboquant_index does on Mcpg
AI agents use create_turboquant_index to create or update resources in Mcpg, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcpg environment.
Why create_turboquant_index is rated Medium
This tool creates a new index structure in the database, which is a schema modification. While reversible (indexes can be dropped), it commits data structure changes that persist until explicitly removed. This qualifies as Write rather than Execute because it targets a specific database artifact (an index) rather than arbitrary code execution.
From the tool's definition Tool name 'create_turboquant_index' indicates creation of a database index. The 'create_' prefix signals a write operation that modifies schema. PostgreSQL index creation is reversible via DROP INDEX.
Attacks that exploit this kind of access
The rule that runs create_turboquant_index safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcpg, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_turboquant_index, this is the rule to start with:
create_turboquant_index stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcpg, apply this rule, and every create_turboquant_index call is checked against it from then on.
Questions about create_turboquant_index
create_turboquant_index is a write tool on the Mcpg MCP server. It is categorised as a Write tool in the Mcpg MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcpg MCP server in PolicyLayer and add a rule for create_turboquant_index: 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.
create_turboquant_index is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_turboquant_index 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 create_turboquant_index. 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.
create_turboquant_index 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.
This server
Across the catalogue