Suppress a duplicate by WL hash (from analyze output). Only suppress AFTER confirming the duplication is intentional (e.g. API symmetry, test isolation). Refactoring should be the default action for duplicates.
AI agents use suppress 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 suppress tool modifies configuration/state by adding a suppression entry indexed by hash. This is reversible (unsuppress exists as a counterpart) and creates or updates suppression records rather than deleting or executing arbitrary operations. It does not read-only query, execute external code, destroy data, or move money.
From the tool's definition Tool description states it will 'Suppress a duplicate by WL hash', which modifies the state of duplicate detection rules/suppressions.
Documented attack patterns abuse exactly the kind of access suppress 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 suppress:
{
"version": "1",
"default": "deny",
"tools": {
"suppress": {
"limits": [
{
"counter": "suppress_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}suppress 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.
Suppress a duplicate by WL hash (from analyze output). Only suppress AFTER confirming the duplication is intentional (e.g. API symmetry, test isolation). Refactoring should be the default action for duplicates. 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 suppress: 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.
suppress 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 suppress 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 suppress. 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.
suppress 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.