Get the current state of the PDF models(used by get_stored_response_with_markdown) loading process
AI agents call get_model_state to retrieve information from MCP-RQuest without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool fetches status information about an internal process state. It performs only data retrieval without modifying, deleting, or executing external operations. While the parent server can make HTTP requests and bypass anti-bot measures (concerning in aggregate), this specific tool is limited to reading internal model state.
From the tool's definition Tool description indicates it retrieves state information: 'Get the current state of the PDF models(used by `get_stored_response_with_markdown`) loading process'. This is a query/inspection operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_model_state gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP-RQuest, and nothing reaches the server without passing your rules. This is the rule we recommend for get_model_state:
{
"version": "1",
"default": "deny",
"tools": {
"get_model_state": {}
}
}get_model_state is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the current state of the PDF models(used by get_stored_response_with_markdown) loading process. It is categorised as a Read tool in the MCP-RQuest MCP Server, which means it retrieves data without modifying state.
Register the MCP-RQuest MCP server in PolicyLayer and add a rule for get_model_state: 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 MCP-RQuest. Nothing to install.
get_model_state 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_model_state 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_model_state. 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_model_state is provided by the MCP-RQuest MCP server (xxxbrian/mcp-rquest). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 12 MCP-RQuest tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
12 MCP-RQuest tools catalogued and risk-classified — across an index of 42,500+ MCP servers.