query_string_convert
Query-String Parse / Build — Parse a URL query string into params, or build a query string from params (x-www-form-urlencoded, RFC 3986).
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/query-string-convert.md
What query_string_convert does on Gateway
AI agents call query_string_convert to retrieve information from Gateway without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
mode | string | — | parse | build (default parse) |
params | object | — | {key: value|array-of-values} to build (mode=build) |
query_string | string | — | Query string to parse (mode=parse) |
Parameters from the server's own tool schema.
Why query_string_convert is rated Low
This tool performs URL query string parsing and formatting, which are read-only or data-transformation operations. It does not create, modify, delete, execute code, or trigger external operations. Even the 'build' function is simply constructing a string representation from parameters, not persisting data or executing logic.
From the tool's definition Tool description states it 'Parse[s] a URL query string into params, or build[s] a query string from params' — both are data transformation operations with no side effects on external systems or data stores.
Attacks that exploit this kind of access
The rule that runs query_string_convert safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For query_string_convert, this is the rule to start with:
query_string_convert 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 Gateway, apply this rule, and every query_string_convert call is checked against it from then on.
Questions about query_string_convert
Query-String Parse / Build — Parse a URL query string into params, or build a query string from params (x-www-form-urlencoded, RFC 3986). It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
query_string_convert accepts 3 parameters: mode, params, query_string. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for query_string_convert: 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 Gateway. Nothing to install.
query_string_convert 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 query_string_convert 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 query_string_convert. 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.
query_string_convert is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
This server
Across the catalogue