get_packet_filter_list
AI agents call get_packet_filter_list to retrieve information from Sacloud without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix combined with '_list' suffix strongly indicates a read-only operation that retrieves packet filter configurations from Sakura Cloud infrastructure. No side effects are implied by the name. Without a description, confidence is reduced slightly, but the naming pattern is consistent with standard read operations in cloud management APIs.
From the tool's definition Tool name 'get_packet_filter_list' indicates a retrieval operation (get_*_list pattern). The description is empty, but naming convention and sibling tools (create_*, delete_*, attach_*) suggest this is a query/list function without side effects.
Documented attack patterns abuse exactly the kind of access get_packet_filter_list gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sacloud, and nothing reaches the server without passing your rules. This is the rule we recommend for get_packet_filter_list:
{
"version": "1",
"default": "deny",
"tools": {
"get_packet_filter_list": {}
}
}get_packet_filter_list is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_packet_filter_list. It is categorised as a Read tool in the Sacloud MCP Server, which means it retrieves data without modifying state.
Register the Sacloud MCP server in PolicyLayer and add a rule for get_packet_filter_list: 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 Sacloud. Nothing to install.
get_packet_filter_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_packet_filter_list 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 get_packet_filter_list. 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.
get_packet_filter_list is provided by the Sacloud MCP server (sacloud/sacloud-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Sacloud, 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.
37 Sacloud tools catalogued and risk-classified — across an index of 43,000+ MCP servers.