AI agents use paserver_put to create or update resources in Claude Pascal MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Pascal MCP Server environment.
The 'put' naming convention and co-location with 'adb_push' (which uploads files) strongly suggest this performs write/upload operations. If this tool can modify arbitrary files or app data on connected Android devices, an agent could corrupt app state, overwrite critical data, or inject malicious content—justifying 'high' severity.
From the tool's definition Tool name 'paserver_put' suggests a PUT operation (write/upload action). Sibling tools include 'adb_push' and 'adb_pull', establishing a pattern where 'put' operations modify/upload content to Android devices.
Documented attack patterns abuse exactly the kind of access paserver_put gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Pascal MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for paserver_put:
{
"version": "1",
"default": "deny",
"tools": {
"paserver_put": {
"limits": [
{
"counter": "paserver_put_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}paserver_put 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.
Free to start. No card required.
paserver_put. It is categorised as a Write tool in the Claude Pascal MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude Pascal MCP Server MCP server in PolicyLayer and add a rule for paserver_put: 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 Pascal MCP Server. Nothing to install.
paserver_put 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 paserver_put 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 paserver_put. 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.
paserver_put is provided by the Claude Pascal MCP Server MCP server (tina4stack/claude-pascal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Claude Pascal MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
53 Claude Pascal MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.