This record as markdown: /tools/frontmcp/non-cached.md
What non-cached does on Frontmcp
AI agents invoke non-cached to trigger actions in Frontmcp. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why non-cached is rated High
The tool 'simulates a computation' which implies executing some process or operation. The lack of caching suggests it runs fresh each time. However, the word 'simulates' suggests it may not have real side effects. Description is vague, so confidence is moderate. Classified as Execute due to the computation/execution nature, with low severity given it appears to be a simulation without persistent effects.
From the tool's definition Simulates a computation without caching
Attacks that exploit this kind of access
The rule that runs non-cached safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Frontmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For non-cached, this is the rule to start with:
non-cached stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Frontmcp, apply this rule, and every non-cached call is checked against it from then on.
Questions about non-cached
Simulates a computation without caching. It is categorised as a Execute tool in the Frontmcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Front MCP server in PolicyLayer and add a rule for non-cached: 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 Frontmcp. Nothing to install.
non-cached is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the non-cached 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 non-cached. 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.
non-cached is provided by the Front MCP server (agentfront/frontmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Front, and thousands of servers like it.
Across the catalogue