profile_status
Show the active AirMCP profile, module set, tool exposure mode, exposed tool count, and total registered tool count.
This record as markdown: /tools/io-github-heznpc-iconnect/profile-status.md
What profile_status does on Iconnect
AI agents call profile_status to retrieve information from Iconnect without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why profile_status is rated Low
This tool retrieves and displays configuration and status information about the current profile and tool exposure state. It performs no writes, deletes, executes external operations, or financial transactions. The blast radius of misuse is minimal—an adversary gains only visibility into system configuration, not capability to modify or execute anything. Classified as Read with low severity.
From the tool's definition Tool name 'profile_status' and description 'Show the active AirMCP profile, module set, tool exposure mode, exposed tool count, and total registered tool count' indicate data retrieval only.
Attacks that exploit this kind of access
The rule that runs profile_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Iconnect, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For profile_status, this is the rule to start with:
profile_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Iconnect, apply this rule, and every profile_status call is checked against it from then on.
Questions about profile_status
Show the active AirMCP profile, module set, tool exposure mode, exposed tool count, and total registered tool count. It is categorised as a Read tool in the Iconnect MCP Server, which means it retrieves data without modifying state.
Register the Iconnect MCP server in PolicyLayer and add a rule for profile_status: 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 Iconnect. Nothing to install.
profile_status 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 profile_status 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 profile_status. 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.
profile_status is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Iconnect, and thousands of servers like it.
This server
Across the catalogue