performance_baseline
Save current performance metrics as a named baseline for later comparison.
This record as markdown: /tools/alexgladkov-claude-in-mobile/performance-baseline.md
What performance_baseline does on Claude Mobile
AI agents use performance_baseline to create or update resources in Claude Mobile, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Mobile environment.
Why performance_baseline is rated Medium
This tool writes/stores performance data to a persistent baseline record. It creates or modifies saved state (a named baseline) that can be referenced later. It is reversible in nature (baselines can presumably be overwritten or deleted), so Write is appropriate rather than Destructive. Misuse could corrupt performance benchmarking workflows but has limited broader blast radius.
From the tool's definition Save current performance metrics as a named baseline for later comparison
Attacks that exploit this kind of access
The rule that runs performance_baseline safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Mobile, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For performance_baseline, this is the rule to start with:
performance_baseline 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 Claude Mobile, apply this rule, and every performance_baseline call is checked against it from then on.
Questions about performance_baseline
Save current performance metrics as a named baseline for later comparison. It is categorised as a Write tool in the Claude Mobile MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude Mobile MCP server in PolicyLayer and add a rule for performance_baseline: 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 Claude Mobile. Nothing to install.
performance_baseline 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 performance_baseline 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 performance_baseline. 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.
performance_baseline is provided by the Claude Mobile MCP server (alexgladkov/claude-in-mobile). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Claude Mobile, and thousands of servers like it.
This server
Across the catalogue