AI agents use import_terminology to create or update resources in Prometheus MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Prometheus MCP Server environment.
The verb 'import' denotes loading and storing data, which is a reversible write operation. Without a detailed description, we cannot confirm if it modifies existing terminology (Write) or executes arbitrary code (Execute), but the name strongly suggests data ingestion. The confidence is reduced due to the missing description.
From the tool's definition Tool name 'import_terminology' suggests creating or adding terminology data to a system. The empty description limits certainty about exact behavior, but 'import' typically indicates data ingestion/modification rather than deletion or code execution.
Documented attack patterns abuse exactly the kind of access import_terminology gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Prometheus MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for import_terminology:
{
"version": "1",
"default": "deny",
"tools": {
"import_terminology": {
"limits": [
{
"counter": "import_terminology_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}import_terminology 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.
import_terminology. It is categorised as a Write tool in the Prometheus MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Prometheus MCP Server MCP server in PolicyLayer and add a rule for import_terminology: 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 Prometheus MCP Server. Nothing to install.
import_terminology 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 import_terminology 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 import_terminology. 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.
import_terminology is provided by the Prometheus MCP Server MCP server (awslabs.prometheus-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Prometheus 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.
805 Prometheus MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.