AI agents use lsp_setup to create or update resources in Astrograph — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Astrograph environment.
The tool inspects and configures LSP (Language Server Protocol) command bindings. While inspection is a read operation, configuration inherently involves modifying bindings and settings. This is a reversible write operation (configuration can be changed again), not destructive. It lacks code execution or financial aspects.
From the tool's definition Tool performs 'configure' of LSP command bindings, which involves modifying configuration state. The word 'configure' indicates mutation of settings/bindings.
Documented attack patterns abuse exactly the kind of access lsp_setup gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Astrograph, and nothing reaches the server without passing your rules. This is the rule we recommend for lsp_setup:
{
"version": "1",
"default": "deny",
"tools": {
"lsp_setup": {
"limits": [
{
"counter": "lsp_setup_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}lsp_setup 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.
Inspect and configure deterministic LSP command bindings. It is categorised as a Write tool in the Astrograph MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Astrograph MCP server in PolicyLayer and add a rule for lsp_setup: 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 Astrograph. Nothing to install.
lsp_setup 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 lsp_setup 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 lsp_setup. 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.
lsp_setup is provided by the Astrograph MCP server (thaylo/astrograph). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Astrograph, 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.
12 Astrograph tools catalogued and risk-classified — across an index of 43,000+ MCP servers.